mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2711] What is the correct way to pass /tmp/.X11-unix into a chroot? #1707
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#1707
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 @dandelionred on GitHub (May 20, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2711
I debootstrapped ubuntu 19.04 into /nas/chroot/disco and installed smplayer inside.
Running this
I get this
As a dirty fix I set up such bind
and chrooted smplayer can start now.
Is there some native to firejail way to pass /tmp/.X11-unix into a chroot?
Btw I run xorg with
-nolisten localso there is no abstract socket. Hence /tmp/.X11-unix is the only way to X.@smitsohu commented on GitHub (May 20, 2019):
Setting an environment variable
FIREJAIL_X11should work.@dandelionred commented on GitHub (May 20, 2019):
I'm not sure how to use it
@smitsohu commented on GitHub (May 20, 2019):
You need to create an empty
/tmp/.X11-unixdirectory as mount point first.@dandelionred commented on GitHub (May 20, 2019):
Thanks, it works now.
Mby the FIREJAIL_X11 tip should be added to https://firejail.wordpress.com/documentation-2/x11-guide/ ?
@smitsohu commented on GitHub (May 20, 2019):
To be honest,
FIREJAIL_X11is quite a dirty solution itself.In the moment Firejail doesn't help too much in setting up the chroot, but this also means it will not get in your way too much. I think what you described in the original post is "the correct way" actually.
@dandelionred commented on GitHub (May 20, 2019):
KK, got it.
@smitsohu commented on GitHub (May 21, 2019):
A last note:
Don't set
FIREJAIL_X11toyes, any other value will work just fine.@dandelionred commented on GitHub (May 21, 2019):
@smitsohu What is wrong with FIREJAIL_X11=yes?
@smitsohu commented on GitHub (May 21, 2019):
@dandelionred FIREJAIL_X11=yes is used internally to indicate that an
--x*option has been parsed; setting it to a value other than yes navigates around possible issues.Did I already mention it is dirty? 😄