Just do it. They will only get worse
for me it's more that it's heavier than i really need. no hate, i think it's cool software.
Calendar between me and my wife. contacts between various devices, mostly phone.
The internet is healing
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!
yeah, i did try that, but that part failed for some reason. the rest of the Ignition file was ok.
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.
not at this time, thank you. it's more about confirming how MicroOS is functioning with a fresh install and where i need to head from there for rootless functionality. why this isn't the default setup, i don't know.
thank you for confirming my suspicion. i know one CAN give it that power, but i understand that it's not the default.
ultimately, this is a question first about the MicroOS setup, and second podman functionality.
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.