Sure. I do run some things on the host, but I do default to containers unless I have a good reason to avoid them. Containers make it really easy to move to a new piece of hardware, and I want my disaster recovery process to be as close to:
set up new device
restore data
copy down container configs
start containers
Some UPSs communicate over the network, and if that’s what you have, containers are a fantastic solution. If you have a USB or serial (??) one, then yeah, maybe the host will give less trouble, just make sure to not forget to document the setup and config.
You know what makes it really easy to move things around? Proper IaC configuration management in revision control. Build pipelines if you really want to be proper about it with containers.
Using containers as an excuse for “well, I can just move it somewhere else” is the exact reason to not be using containers for absolutely everything. This is the reason why web devs are horrible at infrastructure, and devops is suddenly back in demand. Removing yourself from the actual issues of properly versioning and controlling all your things just to rely on containers is a detriment to actually understand the interactions of what you’re running, where you’re running it.
Sure. I do run some things on the host, but I do default to containers unless I have a good reason to avoid them. Containers make it really easy to move to a new piece of hardware, and I want my disaster recovery process to be as close to:
Some UPSs communicate over the network, and if that’s what you have, containers are a fantastic solution. If you have a USB or serial (??) one, then yeah, maybe the host will give less trouble, just make sure to not forget to document the setup and config.
You know what makes it really easy to move things around? Proper IaC configuration management in revision control. Build pipelines if you really want to be proper about it with containers.
Using containers as an excuse for “well, I can just move it somewhere else” is the exact reason to not be using containers for absolutely everything. This is the reason why web devs are horrible at infrastructure, and devops is suddenly back in demand. Removing yourself from the actual issues of properly versioning and controlling all your things just to rely on containers is a detriment to actually understand the interactions of what you’re running, where you’re running it.