The short introduction on that tutorial is much better than that actual docker site and 10-15 min interactive tutorial on what docker actually is and what it can be used for. A note to other developers, it's a good idea to not use some language without first defining the word... Especially if it's an overloaded term.
I never really got to play extensively with Docker mainly because I have found the setup of OS X not quite friendly. While I understand the value of Docker, basically booting up a VMware/VirtualBox image was faster for my own use.<p>I'll have to give boot2docker a try to see if it is changing things. Having a good guide will definitely help.
When you start playing around with docker and come to the area where you start to see that many things that should be very easy start to be really complicated, then you should take a look at lxc and the upcoming lxd and compare.
Huh, the "Images and layers" section is 404'ing.<p>Edit: ah, here it is - <a href="https://github.com/odewahn/docker-jumpstart/blob/master/public/docker-images.md" rel="nofollow">https://github.com/odewahn/docker-jumpstart/blob/master/publ...</a><p>Edit: filed a PR
Is docker ready for production? Is someone using it on real production environments? Most recipes at Docker Registy are a mess, and with plenty of bugs
Anybody wanting to try out Docker + GoLang + AWS Beanstalk, I've made a sample app / guide here - <a href="https://github.com/OrganicCoffeeNepal/DockerBeanstalkSample" rel="nofollow">https://github.com/OrganicCoffeeNepal/DockerBeanstalkSample</a>
The new Nitrous Pro (<a href="https://pro.nitrous.io" rel="nofollow">https://pro.nitrous.io</a>) has a docker template you can use if you don't feel like installing boot2docker locally.<p>There's also a bunch of advanced docker options you can check out:<p><a href="http://docs.nitrous.io/v1.0/docs/advanced-container-management-options" rel="nofollow">http://docs.nitrous.io/v1.0/docs/advanced-container-manageme...</a><p>Would be a good compliment to the docker jumpstart manual.
There is some outdated information on this site for boot2docker on Mac OS X.<p>1. You need to set more than just tcp://ip:2376. You need to run<p>$ eval $(boot2docker shellinit)<p>to also set vars for DOCKER_CERT_PATH<p>2. In order to get proper forwarding from your host Mac OS X to your boot2docker-vm, you use -P as a command line option for any containers you 'run'.<p>Bonus docker gotcha:<p>docker containers can't make fsync() calls on shared folders between your Mac and the boot2docker-vm. This means a lot of database software can't use a shared folder to store a database.