11–20 of 45 posts
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. I'll have to give boot2docker a try to see if it is changing things. Having a good guide will definitely help.
Machine makes it really easy to create Docker hosts on your
computer, on cloud providers and inside your own data center.
It creates servers, installs Docker on them, then configures
the Docker client to talk to them.
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. I'll have to give boot2docker a try to see if it is changing things. Having a good guide will definitely help.
Give Docker Machine a try https://docs.docker.com/machine/ Machine makes it really easy to create Docker hosts on your computer, on cloud providers and inside your own data center. It creates servers, installs Docker on them, then configures the Docker client to talk to them. Kitematic is another option https://kitematic.com
1. You need to set more than just tcp://ip:2376. You need to run
$ eval $(boot2docker shellinit)
to also set vars for DOCKER_CERT_PATH
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'.
Bonus docker gotcha:
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.
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. I'll have to give boot2docker a try to see if it is changing things. Having a good guide will definitely help.
There is some outdated information on this site for boot2docker on Mac OS X. 1. You need to set more than just tcp://ip:2376. You need to run $ eval $(boot2docker shellinit) to also set vars for DOCKER_CERT_PATH 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'. Bonus docker gotcha: docker containers can't make fsync()…
There is some outdated information on this site for boot2docker on Mac OS X. 1. You need to set more than just tcp://ip:2376. You need to run $ eval $(boot2docker shellinit) to also set vars for DOCKER_CERT_PATH 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'. Bonus docker gotcha: docker containers can't make fsync()…
It's all a little outdated - 9 months is a long time in the Docker world.
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.
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.
For a good 2-3 sentences description I go on Wikipedia when available.