3 ms·
So I actually remember running into the "Unable to locate package docker-engine" issue a while ago, and it seemed like an issue on Docker's end because for me,
by lewisl9029 11y ago
So I actually remember running into the "Unable to locate package docker-engine" issue a while ago, and it seemed like an issue on Docker's end because for me, the issue actually only lasted about half a day before it started working again without any changes on my part.
So I think in the end this was just a case of really unfortunate timing, because if it weren't for the Docker installation issue, the only real complaint left in this post would have been the fact that the official method of installing Docker was to curl a script and pipe into sh[1]. And the rest of the post would have been singing praises of how amazing Docker is to be able to take setting up a Rails app along with all its dependencies and turn it into such a simple, painless process.
[1] Which is a perfectly valid criticism, by the way. They should really document the much saner method of installing through their official repos:
https://blog.docker.com/2015/07/new-apt-and-yum-repos/ https://blog.docker.com/2015/07/new-apt-and-yum-repos/
- mkozlows 11y agoYeah, the really weird thing about this article is that it's all snarky about Docker, and then it goes off into weird manual-install land (which makes about as much sense as saying "I couldn't get the .msi installer to run, so I started copying files around and registering DLLs by hand" -- maybe you'll get that to work eventually, but it's never going to be pleasant), and then makes a call for something that... solves the problems Docker solves. The whole article is basically a "there has to be an easier way!" infomercial for Docker, only it doesn't realize it.
- Gigablah 11y agoIt's funny because the project actually provides a Vagrantfile for creating a regular VM image.
- codinghorror 11y agoVagrant's only intended as a development solution, though, not for production deployment.