3 ms·
If you have machines with unused capacity, why would deploying a docker container image be easier than deploying a RPM package?
by concede_pluto 9y ago
If you have machines with unused capacity, why would deploying a docker container image be easier than deploying a RPM package?
- wmf 9y agoBecause either there is no RPM or the RPM conflicts with other RPMs on the machine.
- dkarapetyan 9y agoSounds like then you should learn what a chroot is. All the existing linux platforms already provide the solution to your exact problem with much less overhead than docker.
- coldtea 9y agoOnly that chroot wont also run on the development machine, running a totally different OS.
- concede_pluto 9y agoThis is a self-inflicted problem. 787 engineers don't have to test their work on a Learjet.
- chubot 9y agoI agree this is possible, but the tools are somewhat obscure and slow. You can debootstrap in a chroot and then install packages, but it takes a long time, and likely re-downloads hundreds of megabytes packages you already have on the system. I don't like Docker, but I think it does some differential compression with the layers when you are modifying the image. So you don't have to re-do this install from scratch. You may also run into issues with user IDs and various system config files in the chroot. Configuring the service with flags, env vars, and config files is a bit of a pain. Docker is essentially a glorified chroot... I've essentially tried to rebuild it, and it is unfortunately a lot of work.
- darkr 9y agoThere is software collections for RPMs, which is basically namespacing. Can have quite an operational overhead if the thing you want to install has a lot of dependencies though.