[GH-ISSUE #1971] "namespace support is disabled" in 0.9.54 #1326

Closed
opened 2026-05-05 07:52:01 -06:00 by gitea-mirror · 4 comments
Owner

Originally created by @Futureknows on GitHub (May 31, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1971

Running firejail --version I noticed

0.9.52 reports user "namespace support is enabled"
0.9.54 reports user "namespace support is disabled"

Firetools confirms namespace is disable in each firejail running 0.9.54

OS Fedora 27 and Mint reproducible.

Originally created by @Futureknows on GitHub (May 31, 2018). Original GitHub issue: https://github.com/netblue30/firejail/issues/1971 Running `firejail --version` I noticed 0.9.52 reports user "namespace support is enabled" 0.9.54 reports user "namespace support is disabled" Firetools confirms namespace is disable in each firejail running 0.9.54 OS Fedora 27 and Mint reproducible.
gitea-mirror 2026-05-05 07:52:01 -06:00
Author
Owner

@reinerh commented on GitHub (May 31, 2018):

From where did you get the package? Is it from your distribution or a deb/rpm from firejail?

Also I just see that in platform/rpm/firejail.spec (for building the rpms) userns support is explicitely disabled. Though I don't know why...

<!-- gh-comment-id:393467352 --> @reinerh commented on GitHub (May 31, 2018): From where did you get the package? Is it from your distribution or a deb/rpm from firejail? Also I just see that in platform/rpm/firejail.spec (for building the rpms) userns support is explicitely disabled. Though I don't know why...
Author
Owner

@SkewedZeppelin commented on GitHub (May 31, 2018):

@reinerh
It was disabled here in early 2016.

I tested with it enabled:

  • under Fedora 28 it works fine
  • under CentOS 7 the message is printed "Warning: cannot create a new user namespace, going forward without it...", and then continues just fine

If its just a minor warning under some systems and there are benefits to having it enabled I see no reason to not enable it again.

<!-- gh-comment-id:393476096 --> @SkewedZeppelin commented on GitHub (May 31, 2018): @reinerh It was disabled [here](https://github.com/netblue30/firejail/commit/1bb8fddae5c92dde1ba750f50e80b306dd9cc6a0#diff-c95419737801a34f6c1c0dc5213ff1a9R22) in early 2016. I tested with it enabled: - under Fedora 28 it works fine - under CentOS 7 the message is printed "Warning: cannot create a new user namespace, going forward without it...", and then continues just fine If its just a minor warning under some systems and there are benefits to having it enabled I see no reason to not enable it again.
Author
Owner

@netblue30 commented on GitHub (Jun 4, 2018):

CentOS 7 has a kernel 3.10 with a totally broken user namespace, so I disabled it when building rpm packages to be posted on SourceForge as part of the release. It should work fine on newer kernels on Fedora, but you have to compile it yourself.

<!-- gh-comment-id:394479216 --> @netblue30 commented on GitHub (Jun 4, 2018): CentOS 7 has a kernel 3.10 with a totally broken user namespace, so I disabled it when building rpm packages to be posted on SourceForge as part of the release. It should work fine on newer kernels on Fedora, but you have to compile it yourself.
Author
Owner

@Futureknows commented on GitHub (Jun 6, 2018):

Thanks! Can confirm fresh compiled 0.9.55 enables namespace support in Fedora and Ubuntu.

<!-- gh-comment-id:394925186 --> @Futureknows commented on GitHub (Jun 6, 2018): Thanks! Can confirm fresh compiled 0.9.55 enables namespace support in Fedora and Ubuntu.
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#1326
No description provided.