fantastic, thank you!
yeah, when they said it was “ready for podman” i, uh, expected a little more preconfig. XD
as an aside, re: point 3, port forwarding won’t work in firewalld? like , 80->8080, then 8080->container?
fantastic, thank you!
yeah, when they said it was “ready for podman” i, uh, expected a little more preconfig. XD
as an aside, re: point 3, port forwarding won’t work in firewalld? like , 80->8080, then 8080->container?
it does, thanks! i’m mostly really surprised that MicroOS hasn’t prepared all of this ahead of time for something that’s supposed to be a “ready for podman containers” install.
i’m definitely root, which is the sole default user on MicroOS for login, bash, etc.
it mostly strikes me as odd that MicroOS for containers would not have me setup a non-root user at install. trying to do it after install necessitates some hoop jumping to get podman to work correctly, which is making me wonder if MicroOS is really worth it at that point if it’s not ready to go after install.
i’ve been ass-deep in doc and guides for days, mate. can you just answer the question if you know the answer?
rootless podman should not be able to bind to port 80, for example. but i CAN do this on MicroOS. which is making me think that it’s running rootful. and if that’s happening because i’m working under the sole root user in MicroOS.
thanks, very helpful! your comment is definitely relevant, and i hope this topic will help others in the future who may be confused about best practice w/ MicroOS.
for what it’s worth, i did end up running Rootful!