this post was submitted on 22 Feb 2024
105 points (91.3% liked)

Linux

48310 readers
645 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

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
105
it's not always sunny with podman (lemmy.ml)
submitted 9 months ago* (last edited 9 months ago) by GravitySpoiled@lemmy.ml to c/linux@lemmy.ml
46 comments fedilink hide all child comments
 

I am moving from docker to podman and selinux because I thought that podman is more secure and hence, the future. I thought the transition will be somewhat seamless. I even prepaired containers but once I migrated I still ran into issues.

minor issue: it's podman-compose instead of podman compose. The hyphen feels like a step back because we moved from docker-compose to docker compose. But thT's not a real issue.

podman does not autostart containers after boot. You have to manually start them, or write a start script. Or create a systemd unit for each of them.

Spinning up fresh services works most of the time but using old services that worked great with docker are a pain. I am wasting minutes after minutes because I struggle with permissions and other weird issues.

podman can't use lower number ports such that you have to map the ports outside of the machine and forward them properly.

Documentation and tutorials are "all" for docker. Github issues are "all" for docker. There isn't a lot of information floating around.

I'm still not done and I really wonder why I should move forward and not go back to docker. Painful experience so far. https://linuxhandbook.com/docker-vs-podman/ and following pages helped me a lot to get rid of my frustration with podman.

you are viewing a single comment's thread
view the rest of the comments
[–] MajinBlayze@hexbear.net 1 points 9 months ago* (last edited 9 months ago) (2 children)

Yeah, podman's networking approach sent me back to docker as well. I have a bunch of services that don't even expose their ports to the local network, they just connect to each other, and only the reverse proxy is exposed. Switching to podman would require me to reconfigure all my port mappings to make sure there aren't any conflicts, and then update all the references. It's not a ton of work, but enough to keep me on docker for the time being.

edit: It looks like podman's networking stack has changed since I used it, so this is almost certainly wrong now

[–] deluxeparrot@thelemmy.club 1 points 9 months ago (1 children)

Is there a difference between networking approaches?

With rootful podman containers the only difference I noticed is that bridge networks aren't isolated by default.

Why would you need to reconfigure the port mappings?

[–] MajinBlayze@hexbear.net 2 points 9 months ago

Tbh it's possible I messed something up, iirc the bridge network I was using wouldn't work, and it seemed like it would only work in host mode, hence the belief that I needed to remap things. This was over a year ago, and tbh I didn't try very hard to make it work.