this post was submitted on 28 Aug 2026
96 points (100.0% liked)

libre

10241 readers
3 users here now

Welcome to libre

A comm dedicated to the fight for free software with an anti-capitalist perspective.

The struggle for libre computing cannot be disentangled from other forms of socialist reform. One must be willing to reject proprietary software as fiercely as they would reject capitalism. Luckily, we are not alone.

libretion

Resources

  1. Free Software, Free Society provides an excellent primer in the origins and theory around free software and the GNU Project, the pioneers of the Free Software Movement.
  2. Switch to GNU/Linux! If you're still using Windows in $CURRENT_YEAR, try a GNU/Linux distribution.

Rules

  1. Be on topic: Posts should be about free software and other hacktivst struggles. Topics about general tech news should be in the technology comm or programming comm. That doesn't mean all posts have to be serious though, memes are welcome!
  2. Avoid using misleading terms/speading misinformation: Here's a great article about what those words are. In short, try to avoid parroting common Techbro lingo and topics.
  3. Avoid being confrontational: People are in different stages of liberating their computing, focus on informing rather than accusing. Debatebro nonsense is not tolerated.
  4. All site-wide rules still apply

Artwork

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] PorkrollPosadist@hexbear.net 10 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

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.

[–] edie@lemmy.encryptionin.space 5 points 1 week ago* (last edited 1 week ago) (2 children)

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.

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.

[–] hello_hello@hexbear.net 4 points 1 week ago (1 children)

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.

[–] edie@lemmy.encryptionin.space 2 points 1 week ago* (last edited 1 week ago) (1 children)

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.

[–] hello_hello@hexbear.net 4 points 1 week ago

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.

[–] PorkrollPosadist@hexbear.net 3 points 1 week ago* (last edited 1 week ago)

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.

[–] decaptcha@hexbear.net 2 points 1 week ago

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