Like most people, I saw the announcement for Docker Machine and decided that I’ve been reading about Docker long enough, I should really take a look at it. And Docker Machine sounded like a dream come true, so I decided why not give it a try since it sounded so easy. So I followed the instructions and downloaded the packages I needed and tried to create my first “dev” machine, unfortunately, I did not get a nice happy Docker Machine ready for use – instead I got the following output:
INFO Downloading boot2docker... INFO Creating SSH key... INFO Creating VirtualBox VM... INFO Starting VirtualBox VM... INFO Waiting for VM to start... FATA open /Users/me/.docker/public-key.json: no such file or directory
And apparently, I’m not the first person to report this as there is already a GIT issue for it:
Add instruction to create the public key
So that makes a lot of sense now. So I tried running the command suggested:
But I get a message about not specifying a command for the call to “docker”. Luckily, it apparently created the public key and now when I try to create a new machine, I get the following:
INFO Downloading boot2docker... INFO Creating SSH key... INFO Creating VirtualBox VM... INFO Starting VirtualBox VM... INFO Waiting for VM to start... INFO "dev" has been created and is now the active machine. To point Docker at this machine, run: export DOCKER_HOST=$(machine url) DOCKER_AUTH=identity
Victory is mine! Okay, hope this helps someone and I hope I get to find some time to continue playing around with Docker. I’m also hoping to get a site up and running on Digital Ocean sooner rather than later as well. Then I can try this whole container portability thing and see what all the hype is about. Stay tuned.