102
it's not always sunny with podman
(lemmy.ml)
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 22 Feb 2024
102 points (91.1% liked)
Linux
48325 readers
644 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 5 years ago
MODERATORS
Your issues stem from going rootless. Podman Compose creates rootless containers and that may or may not be what you want. A lot more configuration needs to be done to get rootless containers working well for persistent services that use low ports, like enabling linger for specific users or enabling low ports for non-root users.
If you want the traditional Docker experience (which is rootful) and figure out the migration towards rootless later, I'd recommend the following:
podman-docker. This provides a seamless Docker compatibility layer for podman, allowing you to even use regular docker commands that get translated behind the scenes into Podman.docker-compose. This will work viapodman-dockerand gives you the native docker compose experience.podman.socketandpodman-restart.service. First one socket-activates the central Podman daemon, second one restarts any podman containers with arestart-policyofalwayson boot.sudo, sosudo docker-compose up -detc. You can run this withsudo podman composeas well if you're allergic to hyphenation. Podman allows both rootful and rootless containers and the way you choose is by running the commands withsudoor not.This gets you to a very Docker-like experience and is what I am currently using to host my services. I do plan on getting familiar with rootless and systemd services and Kubernetes files, but I honestly haven't had the time to figure all that out yet.
thank you!
Thanks, the last time I checked I was told that creating individual systemd services was the only viable solution and I ended up ditching podman because I didn’t think it was worth the hassle. I might try it again with your tips.
Definitely not necessary. If that was the case, it wouldn't live up to it's claims of being a transparent Docker replacement at all. I think you do need to use systemd if you want to go full rootless, but I haven't tried it enough to make a solid call on that.
But yeah, with the above steps, I've moved seamlessly over to Podman for my self hosting stack and I've never looked back. It's also great because I can take literally any Docker Compose I find on the Internet and it will most likely just work.