If you’re using Docker, Debian should be fine. The containers include their own runtimes and make the software running on the host mostly irrelevant. For what its worth, I run matapacos.dog on Debian (without Docker). You couldn’t ask for a better server OS in my opinion.
You seem to be a knowledged linuxer, do you know how to make docker compose containers start on boot. Last I used it I think I had to log on and run docker compose up -d every time.
There’s also the Podman way of doing things which involve using Podman Quadlets/Pods to group containers together and to start them as a rootless systemd user service (using loginctl’s enable-linger toggle to allow services to be started without the user being logged in.
I was looking at podman. And I was interested in it, though I wasn’t certain if I wanted to use it since I was going to be doing docker compose stuff. Is there more you could tell me about it?
ⓘ This user is suspected of being a cat. Please report any suspicious behavior.
Certainly. Podman is essentially a daemonless re-implementation of docker that integrates better with GNU/Linux systems. It uses the same Open Containers Initiative (OCI) framework and can be used a drop-in replacement to docker.
The benefit of using podman is that it doesn’t require a daemon by default which makes it more resilient than docker and simpler to set up. You can migrate any docker-compose setup to podman via the podman-compose plugin but you can also use pods (Kubernetes-speak) to deploy connected services.
For example, you can use podman-compose to generate a systemd unit file or use --in-pod to create a pod from a compose file.
I actually have very little practical experience with Docker beyond a high level understanding of how it works. In my experience, activating the docker systems unit was sufficient.
Thanks, makes perfect sense. Think my brain was trying to save itself from pondering the work involved in moving the containers over. My oldest ones I set up before I really knew what I was doing so I’m expecting it to be a chore to backup, migrate, and adopt them into the management container I’m using now (Arcane). Would make a nice weekend project if I had one to spare, hehe
If you’re using Docker, Debian should be fine. The containers include their own runtimes and make the software running on the host mostly irrelevant. For what its worth, I run matapacos.dog on Debian (without Docker). You couldn’t ask for a better server OS in my opinion.
You seem to be a knowledged linuxer, do you know how to make docker compose containers start on boot. Last I used it I think I had to log on and run
docker compose up -devery time.Edit: I should have just asked the search engine which leads me to stackoverflow. See also dockers own docs on restart
ⓘ This user is suspected of being a cat. Please report any suspicious behavior.
There’s also the Podman way of doing things which involve using Podman Quadlets/Pods to group containers together and to start them as a rootless systemd user service (using loginctl’s
enable-lingertoggle to allow services to be started without the user being logged in.I was looking at podman. And I was interested in it, though I wasn’t certain if I wanted to use it since I was going to be doing docker compose stuff. Is there more you could tell me about it?
ⓘ This user is suspected of being a cat. Please report any suspicious behavior.
Certainly. Podman is essentially a daemonless re-implementation of docker that integrates better with GNU/Linux systems. It uses the same Open Containers Initiative (OCI) framework and can be used a drop-in replacement to docker.
The benefit of using podman is that it doesn’t require a daemon by default which makes it more resilient than docker and simpler to set up. You can migrate any docker-compose setup to podman via the
podman-composeplugin but you can also use pods (Kubernetes-speak) to deploy connected services.For example, you can use
podman-composeto generate a systemd unit file or use--in-podto create a pod from a compose file.I actually have very little practical experience with Docker beyond a high level understanding of how it works. In my experience, activating the docker systems unit was sufficient.
Thanks, makes perfect sense. Think my brain was trying to save itself from pondering the work involved in moving the containers over. My oldest ones I set up before I really knew what I was doing so I’m expecting it to be a chore to backup, migrate, and adopt them into the management container I’m using now (Arcane). Would make a nice weekend project if I had one to spare, hehe