はてなブックマーク

TL,DR: I have left Docker Inc. to take a sabbatical and recover from depression and burnout. I plan to dedicate the next six months to family, friends, meditation, music, and generally speaking, enjoy life to recharge for whatever will come next. This text is an adaptation of the message that I sent last week to my coworkers to announce my departure. I’m now sharing it with a wider audience, becau

We have moved! The orchestration workshop materials can now be found at: http://container.training/ Thank you!

In a Dockerfile, if you put data in a directory, and then declare that directory to be a volume, weird things can happen. Let’s see what exactly. The problem Someone contacted me to ask about very slow build times. They told me: “This is weird. In this Dockerfile, the VOLUME and CMD lines take a few minutes. Why is that?” The diagnostic I was very intrigued, and investigated. And I found the reaso

class: center, middle # Deep dive into # Docker storage drivers ## * ## Jérôme Petazzoni - @jpetazzo ## Docker - @docker --- class: center, middle # .small[Not so deep] dive into # Docker storage drivers ## * ## Jérôme Petazzoni - @jpetazzo ## Docker - @docker --- # Who am I? - [@jpetazzo](https://twitter.com/jpetazzo) - Tamer of Unicorns and Tinkerer Extraordinaire.red[¹] - Grumpy French DevOps p

~jpetazzo/If you run SSHD in your Docker containers, you're doing it wrong! When they start using Docker, people often ask: “How do I get inside my containers?” and other people will tell them “Run an SSH server in your containers!” but that’s a very bad practice. We will see why it’s wrong, and what you should do instead. Note: if you want to comment or share this article, use the canonical versi

When they start using Docker, people often ask: “How do I get inside my containers?” and other people will tell them “Run an SSH server in your containers!” but that’s a very bad practice. We will see why it’s wrong, and what you should do instead. Note: if you want to comment or share this article, use the canonical version hosted on the Docker Blog. Thank you! Your containers should not run an S

If you upgraded your Docker installation to 0.9, you are now using libcontainer to run your containers. And if you were using lxc-attach, you probably noticed that it doesn’t work anymore. Here are two ways to recover the “attach” feature with Docker containers. What happened? First, let’s explain exactly what’s involved here. Before 0.9, Docker was using the LXC userland tools to start 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. By default, this plugin will store all your containers in a 100 GB sparse file, and each container will be limited to 10 GB. This article will explain how you can change that limit, and move container storage to a dedicated par