github-starred/firejail

Fork 0

mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00

[GH-ISSUE #452] Warning: failed to unmount /sys #322

New issue

Closed

opened 2026-05-05 05:36:01 -06:00 by gitea-mirror · 8 comments

gitea-mirror commented

2026-05-05 05:36:01 -06:00

Owner

Originally created by @requiredregistration on GitHub (Apr 18, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/452

does this mean that --overlay and --overlay-tmpfs will not work as expected?

Originally created by @requiredregistration on GitHub (Apr 18, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/452 does this mean that --overlay and --overlay-tmpfs will not work as expected?

gitea-mirror

2026-05-05 05:36:01 -06:00

closed this issue
added the
information_old
label

gitea-mirror commented

2026-05-05 05:36:05 -06:00

Author

Owner

@netblue30 commented on GitHub (Apr 18, 2016):

Don't worry about them for now, there is something strange with the way overlayfs kernel feature uses /sys. I will probably suppress the warnings.

@netblue30 commented on GitHub (Apr 18, 2016): Don't worry about them for now, there is something strange with the way overlayfs kernel feature uses /sys. I will probably suppress the warnings.

gitea-mirror commented

2026-05-05 05:36:08 -06:00

Author

Owner

@requiredregistration commented on GitHub (Apr 18, 2016):

it might be an overlayfs bug. maybe we should report it to the kernel people.

@requiredregistration commented on GitHub (Apr 18, 2016): it might be an overlayfs bug. maybe we should report it to the kernel people.

gitea-mirror commented

2026-05-05 05:36:09 -06:00

Author

Owner

@requiredregistration commented on GitHub (May 2, 2016):

you closed it without explaining why.

when you say that something is strange with the overlayfs, that means you do not understand it perfectly or there is a bug.

closing the issue does not answer the question of if there is a problem here because of your lack of knowledge or because there is a kernel bug.

@requiredregistration commented on GitHub (May 2, 2016): you closed it without explaining why. when you say that something is strange with the overlayfs, that means you do not understand it perfectly or there is a bug. closing the issue does not answer the question of if there is a problem here because of your lack of knowledge or because there is a kernel bug.

gitea-mirror commented

2026-05-05 05:36:11 -06:00

Author

Owner

@netblue30 commented on GitHub (May 2, 2016):

I cannot do anything about it, I think it has something to do with the kernel, so I am not going to carry it as a bug. I have it on my watch list, if ever some more information becomes available.

@netblue30 commented on GitHub (May 2, 2016): I cannot do anything about it, I think it has something to do with the kernel, so I am not going to carry it as a bug. I have it on my watch list, if ever some more information becomes available.

gitea-mirror commented

2026-05-05 05:36:12 -06:00

Author

Owner

@requiredregistration commented on GitHub (May 3, 2016):

by sending an e-mail to the LKML we can learn why.

@requiredregistration commented on GitHub (May 3, 2016): by sending an e-mail to the LKML we can learn why.

gitea-mirror commented

2026-05-05 05:36:14 -06:00

Author

Owner

@requiredregistration commented on GitHub (May 29, 2016):

maybe the overlayfs log can help you discover why you see unexpected and/or wrong behavior.

you have labeled it 'information', so it won't be tracked as a 'bug'. it should have never been closed. keep it open until we learn the reason that this happens.

@requiredregistration commented on GitHub (May 29, 2016): maybe the [overlayfs log](https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/fs/overlayfs) can help you discover why you see unexpected and/or wrong behavior. you have labeled it 'information', so it won't be tracked as a 'bug'. it should have never been closed. keep it open until we learn the reason that this happens.

gitea-mirror commented

2026-05-05 05:36:15 -06:00

Author

Owner

@tobwen commented on GitHub (Jun 10, 2018):

Warning still appears on Debian GNU/Linux 9.4 (stretch) with firejail version 0.9.54

@tobwen commented on GitHub (Jun 10, 2018): Warning still appears on Debian GNU/Linux 9.4 (stretch) with firejail version 0.9.54

gitea-mirror commented

2026-05-05 05:36:17 -06:00

Author

Owner

@smitsohu commented on GitHub (Aug 29, 2018):

Just for clarification: This warning was issued by firejail and not by the kernel or some system service. The reason is that were trying to unmount sysfs at a timepoint when it was not mounted.

This will be fixed in 0.9.56

@smitsohu commented on GitHub (Aug 29, 2018): Just for clarification: This warning was issued by firejail and not by the kernel or some system service. The reason is that were trying to unmount sysfs at a timepoint when it was not mounted. This will be fixed in 0.9.56

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#322

No description provided.

Rows
Columns