Repository navigation
Directory at /proc/{PID}/root doesn't match root of the sandbox #589
Description
Activity
WFM
Can you give more STR like bwrap command (as minimal as reproducible at best) and how you find the pid.
bwrap --unshare-all --share-net --symlink usr/lib /lib --symlink usr/lib64 /lib64 --symlink usr/bin /bin --symlink usr/sbin /sbin --ro-bind /usr /usr --ro-bind /etc /etc --dev /dev --proc /proc --dir /tmp --new-session --ro-bind-data 3 /.flatpak-info bash 3<<EOF [Application] name=org.mozilla.firefox EOF
$ ps -efH [...] rusty-snake 380653 [...] bwrap --unshare-all --share-net --symlink usr/lib /lib --symlink usr/lib64 /lib64 --symlink usr/bin /bin --symlink usr/sbin /sbin --ro-bind /usr /usr --ro-bind /etc /etc --dev /d rusty-snake 380654 [...] bwrap --unshare-all --share-net --symlink usr/lib /lib --symlink usr/lib64 /lib64 --symlink usr/bin /bin --symlink usr/sbin /sbin --ro-bind /usr /usr --ro-bind /etc /etc --dev rusty-snake 380655 [...] bash ^^^^^^ [...] $ cat /proc/380655/root/.flatpak-info [Application] name=org.mozilla.firefox
required for portals to work correctly
- required for portals to work correctly with flatpaks
- for everything else that is not a flatpak, it is a hacky workaround to make one thing work and break two others or break your system (e.g. "if I copy it to my root directory as .flatpak-info, well things start getting funny with my desktop").
- Just to be clear that this is not something officially supported or recommended by the x-d-p authors.
Closing this since I realized it was user error
While debugging some issues related to portals (flatpak/xdg-desktop-portal#1076), it seems like the
rootfolder in/proc/{PID}(wherePIDis the PID of the command ran bybwrap) doesn't match what is expected in the sandboxed environment, which causes issues when trying to use portals.For instance, I have a
.flatpak-infofile in the root folder of the sandboxed environment (required for portals to work correctly), but said file does not appear in therootfolder of/proc/{PID}.Of course the program still reports the filesystem correctly, but other programs like
xdg-desktop-portalwill behave differently then intended