this post was submitted on 24 Aug 2026
496 points (93.5% liked)

linuxmemes

32704 readers
275 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry of any kind will not be tolerated. This is an LGBTQ+-friendly community -- if that is a problem for you, you should leave.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves / tolerates / hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. 🇬🇧 Language/язык/Sprache
  • This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 3 years ago
    MODERATORS
     

    EDIT: For some context, I recently gave podman another go. I have a few services on my homelab server set up in docker containers, so I tried migrating to podman.

    After the second major bug (open issue on github) I encountered looked like it would require completely dropping using compose files to work around, I gave up and went back to docker.

    I like the idea of podman, but it’s just not stable. I’ll try again in a year or so.

    As a bonus, docker’s CLI is significantly nicer.

    you are viewing a single comment's thread
    view the rest of the comments
    [–] wylinka@szmer.info 12 points 1 week ago* (last edited 1 week ago) (4 children)

    Through a hacky Python script (podman-compose), but apparently it works. But IMHO there's no reason not to just rewrite compose files as quadlets. I think it's so neat that they work pretty much just like normal systemd units, it makes it feel a lot more logical especially if you're used to pre-container workflows.

    One problem with Podman is that there isn't a lot of newbie-proof documentation, tutorials etc. partially because it's not as popular as Docker and partially because it's developed by Red Hat and they want you to get a RHEL license to access learning resources and support. But if you're good with man pages, this shouldn't be much of a problem, it's easy enough to figure out what to do.

    [–] andho@lemmy.zip 5 points 1 week ago

    I prefer compose for development instead of quadlets. Actually I prefer compose either way although I use quadlets on my server.

    With quadlets all projects files are in the same location and you need separate files for each container, volume, network, etc.

    They don't just work pretty much like systemd units; they are generated into systemd units

    [–] not@lemmy.dbzer0.com 4 points 1 week ago

    Couldn't someone like you type up a short list with tips and tricks and post it where the newbies can find it?

    [–] anyhow2503@lemmy.world 1 points 1 week ago (1 children)

    I would recommend using the docker-compose cli pointed at a podman socket over podman-compose. I don't think anyone has been recommending podman-compose for quite a while now.

    [–] EnsignWashout@startrek.website 1 points 1 week ago* (last edited 1 week ago)

    Interesting.

    I used to do it the way you're recommending (before I had podman compose), but I got tired of installing docker compose, and haven't suffered enough for just using Podman compose, lately.

    I do think more things are more likely to work the way you're saying. Compose doesn't seem to be standardized yet? And the original dev was probably using Docker compose - for any randomly selected project.

    But when I can get away with podman compose, I do, as I recall it being much easier to setup.