Anyone else messing with this tool? I dove into it today after having read a few things over the last few months. We're ramping up development on a new system and nailing down the architecture, and I wanted to see if Docker could deliver on its promise of packaging up a complete environment and all its dependencies in a lightweight container that we could pop over to a server.
I have to say I was kind of blown away. If I was running Linux as my main system this could probably replace VirtualBox for a lot of what I use VMs for now. It's so easy to spin up a container, and they start incredibly fast. Building a saucy 13.10 base image was four bash commands using debbootstrap. The longest wait was just pulling the binaries. Once the image is created a container can be started literally as fast as I can start Sublime Text. It might be faster 🙂.
I haven't figured everything out. Haven't gotten into dockerfiles at all yet. Haven't messed with external mount points. I did manage to get my container to launch with a user other than root, but I could not get .bashrc to execute and set that users environment up. That caused me some momentary consternation because I use .bashrc to set up virtualenv for Python development... and then it occurred to me that Docker basically makes virtualenv obsolete, so who cares? It would still be nice to get the user's init script to run, and it would be nice to run as something other than root inside the container. I know the issue is under discussion on the Google group.
All in all Docker is very cool software, and I can see myself using it for a lot of what I do. Not sure yet whether to rely on it for our production deployment. So if anyone has any insight or input on that specifically would love to hear it.
I have to say I was kind of blown away. If I was running Linux as my main system this could probably replace VirtualBox for a lot of what I use VMs for now. It's so easy to spin up a container, and they start incredibly fast. Building a saucy 13.10 base image was four bash commands using debbootstrap. The longest wait was just pulling the binaries. Once the image is created a container can be started literally as fast as I can start Sublime Text. It might be faster 🙂.
I haven't figured everything out. Haven't gotten into dockerfiles at all yet. Haven't messed with external mount points. I did manage to get my container to launch with a user other than root, but I could not get .bashrc to execute and set that users environment up. That caused me some momentary consternation because I use .bashrc to set up virtualenv for Python development... and then it occurred to me that Docker basically makes virtualenv obsolete, so who cares? It would still be nice to get the user's init script to run, and it would be nice to run as something other than root inside the container. I know the issue is under discussion on the Google group.
All in all Docker is very cool software, and I can see myself using it for a lot of what I do. Not sure yet whether to rely on it for our production deployment. So if anyone has any insight or input on that specifically would love to hear it.
