Last checked and updated on 10 Jun 2026
What Is New in Docker Engine 1.1
Docker Engine 1.1 delivers critical bug fixes and foundational improvements to core components. This release focuses on hardening the runtime and client rather than introducing flashy new features.
| Category | Key Changes |
|---|---|
| Core Improvements | Upgrades to Libcontainer, cgroups, and Namespaces |
| Client & Runtime | New docker events --since flag, improved docker build |
| Bug Fixes | Resolves issues with volumes, networking, and TTY handling |
| Security | Kernel vulnerability mitigation |
What core components were upgraded in 1.1?
The heart of Docker's execution environment got a significant tune-up. This release shipped with newer versions of Libcontainer, cgroups, and Namespaces.
In practice, this means the low-level machinery that handles process isolation is more robust and reliable. You get a more stable foundation for your containers without any visible change in day-to-day commands.
How did the Docker client improve?
The client gained a useful new flag for filtering event history. The docker events --since command now properly accepts a timestamp, allowing you to retrieve events from a specific point in time.
This is a small but meaningful change for automation scripts that need to parse Docker's event log. It saves you from having to manually sift through all historical events to find what you need.
What were the critical bug fixes?
Several pesky issues that could trip up developers were squashed. A major fix resolved problems where data could remain in a container's Volumes even after the container was deleted with docker rm -v.
Other fixes addressed TTY allocation conflicts and networking hiccups. These are the kinds of fixes that reduce those head-scratching "it worked a minute ago" moments during development.
Was there any focus on security?
Yes, this release included mitigations for a kernel vulnerability (CVE-2014-3515) related to filesystem handling. The Docker team patched the engine to prevent potential exploits from within a container.
This underscores the team's focus on runtime security, ensuring the isolation between containers and the host system remains solid. It's a defensive update that keeps your underlying host OS safer.
FAQ
Does Docker 1.1 add any new commands?
No, this was a stabilization release. The focus was on improving existing components like Libcontainer and fixing bugs rather than adding new CLI commands.
I use `docker events` in my scripts. What changed?
The --since flag now correctly accepts a timestamp, making it actually useful for filtering events from a specific time instead of just showing everything.
Should I be concerned about the volume data bug?
If you use data volumes, yes. The bug where docker rm -v sometimes left data behind was fixed. Upgrading ensures your volume cleanup commands work predictably.
Is this release safe for production?
This release is all about hardening and fixing issues, making it more suitable for production than its predecessor. The bug fixes and security patch directly address production-centric concerns.
What was the biggest under-the-hood change?
The upgrade to Libcontainer. This core component manages the low-level Linux kernel features that make containers work, so its improvement makes the entire engine more stable.