Hacker News new | ask | show | jobs
by regularfry 2427 days ago
I can't help but feel that the drive towards docker-style containerisation was fueled by nothing more than the fad for developing on OS X. If you've got an environment where the devs are working on the same OS as production, it becomes much easier to adopt OS packages (whatever flavour that is) as the deployment mechanism, and as a side benefit it becomes easier to set up the dev environment in the first place.

I've done this with Debian, it worked great.
1 comments
kortex 2427 days ago
I work on exactly the same OS as production (ubuntu 18.04) and still need (not want) containers to do my job. One project uses ROS along with different detectors with incompatible dependencies. One takes forever to build from source, and it's way easier to ship around images by pulling from a repo than tranferring binaries and libs.

And even if I didn't have those constraints, I'd still use containers in production because it just makes testing and deployment so much less of a headache.

link
panpanna 2427 days ago
I think there is still a good idea to use the same environment on your own machine.

This doesn't mean it's wrong to use containers to isolate various projects from each other and your main setup.

Edit: I highly recommend using lxd on Ubuntu. It works very well if you have one persistent container per project or large component in a project.

link