mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #731] Kernel fix found for known problem, "Cannot install new software while Firejail is running" #493
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#493
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @david-drinn on GitHub (Aug 18, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/731
This strikes me as exactly the kernel fix needed for the aforementioned firejail known problem:
I wanted to share the knowledge in case it helps you devise a tweak to the way firejail blacklists files, or at the very least so others know which patch they need to backport to older kernels.
@david-drinn commented on GitHub (Aug 18, 2016):
Also, you might look at howsystemd-nspawnbinds directories in containers it spawns. It does not appear to have the aforementioned problem.Incorrect. While
systemd-nspawndoes not bind-ro/etc/passwdetc. by default as firejail does, if you do bind it yourself, or any other such file, you run into the same issue.@netblue30 commented on GitHub (Aug 20, 2016):
Thank you for the info, I'll modify known problem page.