~jpetazzo/

This morning, I watched AWS’ webinar presenting their container service.

It has been asked on #docker-dev recently if it was possible to attach a volume to a container after it was started.

This is my recipe for Gravlax (cured salmon).

This is a simple recipe showing how to run syslog in one container, and then send the syslog messages of multiple other containers to that one.

When they start using Docker, people often ask: “How do I get inside my containers?”

If you build a lot of containers, and have a not-so-fast internet link, you might be spending a lot of time waiting for packages to download.

If you upgraded your Docker installation to 0.9, you are now using libcontainer to run your containers.

If you’re using Docker on CentOS, RHEL, Fedora, or any other distro that doesn’t ship by default with AUFS support, you are probably using the Device Mapper storage plugin.

When you want to install a new machine, or boot in rescue mode, the usual method is to boot from a CD or USB stick.

There are many ways to handle Python app dependencies with Docker.

Earlier this month, I attended the first Flynn meet-up in San Francisco, where the project was presented by its authors.

To help @EstelleDeau to refactor some code, I had a look at introspection and reflection features in IDL.

A mimosa is half a mosa.

By default, the Docker API is exposed over a local UNIX socket.

A recurring question on the Docker mailing list and on the Docker IRC channel is “how can I change the network range used by Docker?”.

Linux Containers rely on control groups which not only track groups of processes, but also expose a lot of metrics about CPU, memory, and block I/O usage.

When you install (or upgrade) a service, the package manager will try to start (or restart) this service.

Gunsub means “GitHub Unsubscribe”.

This is the blog I should have setup 15 years ago.