3 ms·
Excited to get the app running, and following the brief instructions of his coworkers, Joe types: docker-compose up His rails bootcamp didn't teach them anyth
by adrianmacneil 11y ago
Excited to get the app running, and following the brief instructions of his coworkers, Joe types:
docker-compose up
His rails bootcamp didn't teach them anything about docker. It turns out docker-compose isn't installed. Not wanting to sound like an idiot, he googles around, and spends 3 hours trying to understand what a "container" is. Many tutorials online mention using boot2docker, but some new people seem to be using docker-machine. He asks Susan which one to use. She sighs, and mentions that the team is split between them.
Eventually he chooses docker-machine, and boots the app up. Now it's unclear where the app is running. Eventually he figures out that he has to run "docker-machine ip default" every time the docker-machine VM starts, so that he knows the IP to visit the development site at something obscure like http://192.168.99.100:5000/ http://192.168.99.100:5000/.
Finally, he makes a change to the code, and refreshes the app page. Nothing happens, because it turns out that his local filesystem is not synced with docker, which is linked through to docker-machine, which is running inside a VM on a virtualbox host.
Don't get me wrong, containers are great. But this sounds like more of an argument for good "getting started" documentation, and helpful coworkers, rather than proof that containers are any more simple to get up and running than your average rails app.
- forgotpwtomain 11y ago> Nothing happens, because it turns out that his local filesystem is not synced with docker, which is linked through to docker-machine, which is running inside a VM on a virtualbox host. Not to mention GUI/UID issues when mounting an HFS volume.
- PaulHoule 11y agoIt is not Docker vs Rails or Vagrant or some other technology, it is having that technology really work. From my point of view having a build process where somebody can be productive within an hour of sitting down is part of doing business and it is not hard to attain if it is a goal. That Ruby shop which is so FUBAR in that article is ahead of the curve of the industry as a whole -- it is not unusual for it to take a month or so for somebody to learn to get the build system to work reliably in some places.
- angersock 11y agoBut this sounds like more of an argument for good "getting started" documentation, and helpful coworkers, rather than proof that containers are any more simple to get up and running than your average rails app. This bears repeating: in the second scenario, the new hire had somebody tell them what commands to run. Without that information, they would've been stuck Googling their way to success too. Also, I can't help but be amused at how annoying that homebrew nonsense is--aptitude on Debian is just a hell of a lot simpler.
- lyime 11y agoWhat's "non-sense" about it?