Oh, alright! I didn’t know that. Thank you for the info, that’s handy to know.

Maybe because it’s not an obviously wanted feature? But I’m just guessing. You should request it and see what happens, maybe more people want it. I’ve never even thought about it, since in the case of Podman/docker it’s so “obvious” and easy to just mount network shares to the host first. And in the case of Kubernetes you can just mount NFS shares directly into pods.

Agreed, but not quite perfectly. I’ve been using Tumbleweed for years, but there are a few things to think about.

Whereas I’ve very rarely experienced any problems, the package manager is slow compared to the likes of apt and dnf. The repos are large, but the mirrors haven’t always been the fastest for me.

Also “community”. There are always people in OpenSUSE matrix/irc rooms etc, but they are a rather small bunch of people. OpenSUSE doesn’t have close to the community of, say, Ubuntu or Arch.

I definitely do not hate SELinux, I think it’s a great system. But my experience mostly (at home, anyway) comes from managing servers running Kubernetes clusters and, like, just using podman do deploy containers. In both these cases SELinux is a on “just works” basis, for the most part.

Then in enterprise environment that doesn’t run everything on containers, you usually have a very standardized way of applying SELinux policies. At my last place of work we did it via a rather Ansible role. It was simple and easy.

But I can imagine using SELinux at home, where you maybe don’t have these things, might be a rather “mysterious” experience. It’s not the most obvious system.

But learning to write your own policies (even if just trough se2allow or whatever it’s called) does de-mystify SELinix pretty quick.