[GH-ISSUE #1798] hidepid prevents me from viewing firejail-started processes in e.g. htop #1219

Closed
opened 2026-05-05 07:40:39 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @chiraag-nataraj on GitHub (Mar 5, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1798

So I don't know if this is intended behavior. When I start a sandbox, sometimes the resulting processes do not show up in process monitors like top, htop, or ps aux. I think it has to do with the noroot option, since the only ones that do show up are Electron apps, which I cannot use noroot with (libnode.so not found or whatever). Is this intended behavior and, if so, why?

Originally created by @chiraag-nataraj on GitHub (Mar 5, 2018). Original GitHub issue: https://github.com/netblue30/firejail/issues/1798 So I don't know if this is intended behavior. When I start a sandbox, _sometimes_ the resulting processes do not show up in process monitors like `top`, `htop`, or `ps aux`. I think it has to do with the _noroot_ option, since the only ones that _do_ show up are Electron apps, which I cannot use `noroot` with (`libnode.so not found` or whatever). Is this intended behavior and, if so, why?
gitea-mirror 2026-05-05 07:40:39 -06:00
Author
Owner

@chiraag-nataraj commented on GitHub (Mar 5, 2018):

Oh, and the best part is that the processes are owned by me, so they should show up.

<!-- gh-comment-id:370467082 --> @chiraag-nataraj commented on GitHub (Mar 5, 2018): Oh, and the best part is that the processes are owned by me, so they _should_ show up.
Author
Owner

@netblue30 commented on GitHub (Mar 6, 2018):

This happens because of --noroot. It installs a new user namespace with a new user, Even if the new user has the same name as your regular user, for the process handling code in the kernel this is a different user. Interesting, the file system still thinks is the same user, so you have access to your files.

Just use firejail --list, --top etc to list the processes. Also with hidepid you would need to be root to run firemon and firetools.

<!-- gh-comment-id:370823107 --> @netblue30 commented on GitHub (Mar 6, 2018): This happens because of --noroot. It installs a new user namespace with a new user, Even if the new user has the same name as your regular user, for the process handling code in the kernel this is a different user. Interesting, the file system still thinks is the same user, so you have access to your files. Just use firejail --list, --top etc to list the processes. Also with hidepid you would need to be root to run firemon and firetools.
Sign in to join this conversation.
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#1219
No description provided.