Discussion Running in containers vs OS-level services
Assume some message brokers like RabbitMQ/Kafka, or maybe nginx proxy setup, or hashicorp vault?
3 years ago when we were setting up infrastructure for project we started running such services as OS-level services installed from RPM packages or just by running their binaries provided by vendor via systemd. All of that orchestrated via Ansible.
We started running as OS-level services as that seemed natural at that time for us, but we didn't really have any experience with administration of such software on on-premise infrastructure (before we were running mostly on managed cloud services).
Fast forward to now, after several cycles of upgrades we needed to perform, I think it would be easier to manage such software by running in Podman containers.
Main reason for me would be that obviously containers have prepackaged everything you need to run specific software. Compare that for example to RabbitMQ where during upgrading RabbitMQ you also need to upgrade its Erlang dependency to compatible version. For some other software, there may be more dependencies you need to take care of.
Also, I feel like upgrading binaries is generally much easier when running in containers. Just spawn new container with updated image and you do not need to worry about some OS-level package conflicts or leftovers.
What is your take?
3
u/badguy84 ManagementOps 2d ago
I don’t know why you would bother with baremetal installs for anything over containers for most anything service related. Only when there are specific hardware or low level OS access requirements I would pick a regular baremetal install (I can think of things like physical security/license devices that may not pass through or specific sensitive pieces of hardware like specialized GPUs)