Michael

Michael Crosby

Michael Crosby, who has been a Docker open-source contributor since 2013, is the chief maintainer and is responsible for ensuring that community member code and contributions adhere to Docker’s standards. Michael tweets at @crosbymichael.

More by Michael

CPU Management in Docker 1.13

Resource management for containers is a huge requirement for production users. Being able to run multiple containers on a single host and ensure that one container does not starve the others in terms of cpu, memory, io, or networking in an efficient way is why I like working with containers. However, cpu management for containers…

crosby
Michael Crosby

Docker containerd integration

In an effort to make Docker Engine smaller, better, faster, stronger, we looked for components of the current engine that we can break out into separate projects and improve along the way. One of those components is the Docker runtime for managing containers. With standalone runtimes like runc, we need a clean integration point for adding…

crosby
Michael Crosby

Containerd: a daemon to control runC

As we build out Docker’s infrastructure plumbing, we are committed to releasing these plumbing components as open source to help the community. Today we’re releasing a new daemon to control runC called: containerd. It’s built for performance and density, and will eventually be built into Docker Engine. Containerd is built on top of the Open Container Initiative’s runC…

crosby
Michael Crosby

Docker 0.6.5: name your containers, link them together, selectively publish ports, and more

Review the updates made with Docker 0.6.5 and learn about container naming, links between containers, updated host integration and advanced port redirects.

crosby
Michael Crosby

CPU Management in Docker 1.13

Resource management for containers is a huge requirement for production users. Being able to run multiple containers on a single host and ensure that one container does not starve the others in terms of cpu, memory, io, or networking in an efficient way is why I like working with containers. However, cpu management for containers…

crosby
Michael Crosby

Docker containerd integration

In an effort to make Docker Engine smaller, better, faster, stronger, we looked for components of the current engine that we can break out into separate projects and improve along the way. One of those components is the Docker runtime for managing containers. With standalone runtimes like runc, we need a clean integration point for adding…

crosby
Michael Crosby

Containerd: a daemon to control runC

As we build out Docker’s infrastructure plumbing, we are committed to releasing these plumbing components as open source to help the community. Today we’re releasing a new daemon to control runC called: containerd. It’s built for performance and density, and will eventually be built into Docker Engine. Containerd is built on top of the Open Container Initiative’s runC…

crosby
Michael Crosby

Docker 0.6.5: name your containers, link them together, selectively publish ports, and more

Review the updates made with Docker 0.6.5 and learn about container naming, links between containers, updated host integration and advanced port redirects.

crosby
Michael Crosby