Comment

just_another_person@lemmy.world ⁨2⁩ ⁨days⁩ ago

Containers are an abstraction on top of the OS and hardware that directly communicates with the UPS versus the bare device access needed to communicate via host.

So then you have to run a privileged container for exclusive access to a specific HID port, map said port, and then hope that every OS update you do for whatever your particular container runtime doesnt causes disruptions or comms issues to trigger events on the UPS itself.

Or…just run it on the host and only worry about the NUT server itself. Also to be frank, I don’t imagine that NUT utils in themselves are very container fluid or aware because…why?

I honestly hate that people have become so null to the argument that host things are better at host things. Software that uses direct port access has absolutely no reason to run in a container UNLESS you have no other option. People using containers as default just cuz is bad practice. They have a place and purpose, and this isn’t one of them if host is an option.

source

Sort:hotnew top

sugar_in_your_tea@sh.itjust.works ⁨2⁩ ⁨days⁩ ago
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.
source
- just_another_person@lemmy.world ⁨2⁩ ⁨days⁩ ago
  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.
  
  source