26
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 May 2025
26 points (100.0% liked)
Linux
54324 readers
297 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
I think what OP was describing was writing systemd unit files that would start/stop docker containers.
Exactly, this is what I am doing right now (just for binaries, not execute Docker or Podman).
Yeah, probably, but thats not very common is it? Normally you'd just let the docker daemon handle the start/stop etc?
I actually have no sense how common that is. My experience is with very small non-production docker environments, and with Kubernetes, but I have no idea what people typically do in between.
It's common with rootless docker/podman. Something needs to start up the services, and you're not using a root enabled docker/podman socket, so systemd it is.
Compose files would probably make more sense
Well, someone needs to run
docker compose up
, right? (or you set restart policy, but that's not always possible)You put the restart policy in the compose file