[GH-ISSUE #5306] Error while opening directory: fs.c:476 fs_tmpfs: No such file or directory (Fedora Silverblue) #2951

New issue

Closed

opened 2026-05-05 09:37:00 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 09:37:00 -06:00

Owner

Originally created by @jonleivent on GitHub (Aug 9, 2022).
Original GitHub issue: https://github.com/netblue30/firejail/issues/5306

On Fedora Silverblue, which is an ostree-version of Fedora with /home symlinked to /var/home, firejail (0.9.66) fails:

$ firejail --noprofile --private
...
Error while opening directory: fs.c:476 fs_tmpfs: No such file or directory
Error: proc 3677 cannot sync with peer: unexpected EOF
Peer 3678 unexpectedly exited with status 1

This problem does not occur on standard Fedora, which does not symlink /home. It also does not occur in Silverblue when firejail is not provoked into trying to protect /home (via --private, --private=... etc.).

I am able to get firejail to function within a toolbox (podman container) on Silverblue by removing the symlink and instead mounting /var/home on /home. That probably is unsafe to do outside the toolbox, and is at least not the direction of Silverblue (and whatever other ostree-based distros will follow).

A suggestion to handle these cases would be for firejail to follow the symlink from /home to /var/home, and do whatever protecting/remounting there instead. A general solution would be for firejail to determine where in the symlink-resolved home path for each user in /etc/passwd (a user could have a home anywhere) there is a directory that can be mounted over either to hide that user or to remount home for that user.

Originally created by @jonleivent on GitHub (Aug 9, 2022). Original GitHub issue: https://github.com/netblue30/firejail/issues/5306 On Fedora Silverblue, which is an ostree-version of Fedora with /home symlinked to /var/home, firejail (0.9.66) fails: ``` $ firejail --noprofile --private ... Error while opening directory: fs.c:476 fs_tmpfs: No such file or directory Error: proc 3677 cannot sync with peer: unexpected EOF Peer 3678 unexpectedly exited with status 1 ``` This problem does not occur on standard Fedora, which does not symlink /home. It also does not occur in Silverblue when firejail is not provoked into trying to protect /home (via --private, --private=... etc.). I am able to get firejail to function within a toolbox (podman container) on Silverblue by removing the symlink and instead mounting /var/home on /home. That probably is unsafe to do outside the toolbox, and is at least not the direction of Silverblue (and whatever other ostree-based distros will follow). A suggestion to handle these cases would be for firejail to follow the symlink from /home to /var/home, and do whatever protecting/remounting there instead. A general solution would be for firejail to determine where in the symlink-resolved home path for each user in /etc/passwd (a user could have a home anywhere) there is a directory that can be mounted over either to hide that user or to remount home for that user.

gitea-mirror

2026-05-05 09:37:00 -06:00

closed this issue
added the
duplicate

notabug
labels

gitea-mirror commented

2026-05-05 09:37:03 -06:00

Author

Owner

@rusty-snake commented on GitHub (Aug 9, 2022):

Silverblue/Kinoite is not supported by firejail.

@rusty-snake commented on GitHub (Aug 9, 2022): Silverblue/Kinoite is not supported by firejail.

gitea-mirror commented

2026-05-05 09:37:04 -06:00

Author

Owner

@rusty-snake commented on GitHub (Aug 9, 2022):

#2798, #3025, #3307

@rusty-snake commented on GitHub (Aug 9, 2022): #2798, #3025, #3307

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#2951

No description provided.

Rows
Columns