3 ms·

Packaged and configured are two different things. The fun begins, when you need several applications, which each have different ideas about configuring services

Packaged and configured are two different things. The fun begins, when you need several applications, which each have different ideas about configuring services, that would be otherwise shared. Then, as a matter of convenience, you get packages, that either bundle everything preconfigured to their liking (i.e. gitlab omnibus) or packages, that configure shared services how they need it, and running them shared is not supported (i.e. freeipa, which will configure httpd as it needs and forget having anything else served on the same machine). Docker provides a way to isolate these, so you can still use the same resources you have to run applications, that would not cooperate with each other on a single machine, without having to run separate OS instances in separate VMs.

beagle3 7y ago
I mostly Ubuntu these days, have been for 15 years, and I cannot recall a time installing a package like Freeipa disabled a website installed by other packages. Obviously YMMv and I might have just been lucky.
- vetinari 7y ago
  With freeipa I meant server, not client. Installing is not enough, configuring it into usable state is needed too (i.e. running freeipa-server-install or freeipa-replica-install). It is possible to run other services of such configured httpd, but you need to be careful. When freeipa wanted mod_nss, you had to use mod_nss, not mod_ssl (though they switched it); when freeipa wants to use gssproxy, you are going to use gssproxy too. These changes can happen during upgrades, and it is up to you to fix everything after such change. The project doesn't recommend to run anything else with the same server; you are free to try though. The point was, that with docker or another container system, any such problems are irrelevant, and it allows you to have separate service instances without having to run separate VMs.

beagle3 7y ago

I mostly Ubuntu these days, have been for 15 years, and I cannot recall a time installing a package like Freeipa disabled a website installed by other packages. Obviously YMMv and I might have just been lucky.

vetinari 7y ago
With freeipa I meant server, not client. Installing is not enough, configuring it into usable state is needed too (i.e. running freeipa-server-install or freeipa-replica-install). It is possible to run other services of such configured httpd, but you need to be careful. When freeipa wanted mod_nss, you had to use mod_nss, not mod_ssl (though they switched it); when freeipa wants to use gssproxy, you are going to use gssproxy too. These changes can happen during upgrades, and it is up to you to fix everything after such change. The project doesn't recommend to run anything else with the same server; you are free to try though. The point was, that with docker or another container system, any such problems are irrelevant, and it allows you to have separate service instances without having to run separate VMs.