EU. Doesn't. Need. America.
Don't be afraid. Claim your freedom
I dig immutability for servers, grandma, and productivity laptops.
I think it fills a nice niche in the Linux ecosystem, even if I still prefer my custom prime desktop.
No it is not. Agreeing on that it should be banned is a democratic choice. It is an anti-democratic system not fit for purpose in 2025. our understanding of electoral science and maths is much more advanced now. FPTP should NEVER be on the table.
well, to be fair, shitty electoral systems should be banned, like FPTP, because they aren't representative. what's happening here is sadly the opposite.
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.
Hey all!
I'm looking for recommendations for sharing a Calendar and Contacts.
Any suggestions that aren't OwnCloud/NextCloud? I already have storage with Syncthing and pictures with Immich.
Thanks for your recommendations!
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!
that's great, thanks for sharing! yeah, i love to hear their thoughts on this, since i'm new to ALL of this, immutables and containers. so i want to hear what their design intention is.
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.
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.
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.
edit 2 Addendum
OK, big thanks to @oakcroissant@feddit.org for bringing this to attention here: https://europe.pub/post/390395/686949
that gets to the root (har har) of my confusion here. am i missing the point of MicroOS, or is it the devs who are wrong? 😆
their INTENTION with MicroOS is for us to just use root, which is contrary to how i've lived Linux basically forever.
> Podmans rootless containers are AWESOME on Aeon, where you’re using it interactively and already have none root users.. but that would just be adding unnecessary complications to MicroOS
> MicroOS is designed to use with root, and there is no need to create a non root user for anything.
> IF there was a need to create a non root user then the installer would create a non-root user
which is exactly what was tripping me up. why weren't they facilitating rootless activity, and thus making me jump through hoops to get there.
answer: because it's not needed, and not the intention.
MicroOS: run as root.
------------------- edit Answer
yes, MicroOS only generates a root user at install.
if you want to do rootless containers, you will need to create new, non-root users after.
useradd will NOT generate entries for subuid/subgid by default for the new SYSTEM users.
if the system user already exists, you will need to add them manually:
usermod --add-subuids 100000-165535 <yourusername> usermod --add-subgids 100000-165535 <yourusername>
otherwise, you must use the -F flag with useradd to generate subids for new system users.
thanks all!
--------- hey all! i need a little help here.
i'm just starting to get into self-hosting, and have chosen MicroOS and podman as my environment and tool.
would someone be able to clarify something for me?
I have a MicroOS install for containers, and it seems to only come with a root user. so if i use podman, won't all my pods be rootful?
i try to make a new non-root user, but podman just keeps complaining about privileges when i run it under that user.
so how is this intended to work exactly?
thanks for any help!