NOTE: I can found some app installed in /sysroot/home/gabx/.local. I guess dnf want to install the package here? What I don’t understand is that my home .local is in fact a symlink to a directory on /sysroot where there is still plenty of free space.
$ ls -al /home/gabx/
.....
.local -> /sysroot/home/gabx/.local/
Can anyone tell me how install the package properly, without building/installing it by hand? Or how I can deal with this dnf message about missing space?
It isn’t installed on the host by default, but sometimes it gets pulled in as a dependency when people are doing package layering (i.e. rpm-ostree install)
Yes, I work with servers where Selinux is enabled,and honestly, it is not always trivial. So for my own box, which is not intensively open to the network, I decided to disable it. But I can’t see any reason why enabling Selinux would solve my issue.
I am afraid enforcing it now will mess my system,from what I could read about enforcing after months/years.
I think what’s happening there is that different parts of rpm-ostree make different assumptions about the SELinux state. While rpm-ostree should work with SELinux disabled, it’s definitely not the common scenario (i.e. don’t be surprised if you hit other issues).
Yes, I work with servers where Selinux is enabled,and honestly, it is not always trivial.
I feel your pain there, but once you get used to it it’s not so bad. Especially in Fedora, where SELinux support is pretty good. If you’d really not rather have it enforcing, you’ll still likely have better luck in permissive mode than fully disabling it. That way at least rpm-ostree can still do file labeling.
I may enforce it as I feel quite comfortable with it. I just wanted to avoid for my own box, but if you say I will encounter other issue, let’s go. Last advice: can I enforce it straight now, without any issue?
Somewhat unrelated, but that’s quite a large amount of layered packages. However of course it’s your choice what you layer, but imho the less layered as possible the better.
gcc, git, vim (vi) is in the compose so you don’t need that layered. dnf just isn’t going to work, everything else can either be replaced with flatpak packages or done in toolbox.
Except Chromium, Tweak Tool and zsh.
@gabx Probably just best to set SELInux as permissive, you can still see any possible SELinux errors that way but they won’t block anything.
I didn’t take care of this large amount, but I will try to make some cleaning, especially those who are in the compose. But I am not a huge fan of flatpack as I found some buggy packages.
Any good hint as about layered packages vs compose?
Following Fedora doc, I enabled and set Selinux permissive. I was then able to install the .rpm package
Added:
rstudio-1.2.1565-1.x86_64
But 1- maybe shall it be specified somewhere in the docs it is wise to enable Selinux otherwise some troubles ahead with rpm-ostree? 2- I find it sad to force the user to enable Selinux. I love Linux for the freedom it brings to user to control its machine the way it wants.
Btw, great distro and ty for the good work. I love the immutable part of silverblue. First time I run something else than Archlinux on my homebox since nearly 10 years!
SELinux is enabled out of the box and doesn’t reduce any control, the rules usually only get in the way of normal desktop usage when you start to do weird things (e.g. snap).
I wonder if this is a problem with selinux=disabled. Some messages in the /etc/selinux/config hint that selinux=disabled is actually SELinux enabled with no rules loaded, but it seems like adding selinux=0 to the kernel booting command doesn’t help.