Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Make it easier to link in or bind folders to root directory? #1711
Not sure if this is precisely a project atomic issue or a rpm-ostree issue.
For snap classic one needs to setup a symlink from /snap to/ var/lib/snapd/snap in the root directory but of course the root is readonly.
I made a documentation issue on the snap forums https://forum.snapcraft.io/t/installing-snap-on-fedora/6755/4 but this isn't something rpm-ostree should directly care about I think.
I don't think this is going to be a snap only issue and probably a few other apps will need awkward symlinks like this.
What I'm wondering is if the best way to do this sort of thing is to make a bind mount in the fstab or systemd mount file or if there is an easier way or rpm-ostree can make this sort of thing easier?
Host system details
Provide the output of
Expected vs actual behavior
Would you like to work on the issue?
This is more of a meta or documentation issue of how system administrators are supposed to handle ad-hoc changes like this. Ideally fedora would probably just ship a package snap-classic that installs such a symlink for this specific case but I think other cases like this will probably happen. I know rpm-ostree already has the machinery inside it to merge /etc with /usr/etc and with var.
Not sure what I'm supposed to modify or add a hook to for adding in the ad-hoc change of a symlink. Telling system admins to modify the fstab is okay but a big problem with that is that it is easy to mess up and make the system unbootable (as I did and then had to recover and recovery was annoying because I had to navigate the ostree directory structure.)
That should indeed be it. The OS fs is supposed to be immutable and content provided in a declarative way (i.e. via rpms).
Big picture of course we generally don't want software creating new toplevel directories. Of course both ostree and snap see themselves as "owning" the system and other software is inside it.
There's an old thread that I can't find right now that came up early in Project Atomic where some sysadmins have e.g. NFS mounts at
If it's just about creating a mount point, clearly that's fairly harmless. One can just
That said today rpm-ostree detects and rejects RPMs defining content outside of
Maybe we could define a special
This would allow sysadmins to make local mount points, and for software like snap to define new toplevel dirs which are redirected under
That would be nice. I think we had the same idea over in #337 (comment)