- Feb 26, 2020
-
-
Simon McVittie authored
wrap: mount /usr/share/libdrm if using host libdrm See merge request steam/pressure-vessel!22
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
libdrm reads /usr/share/libdrm/amdgpu.ids to find information about AMD GPUs. So if we are using libdrm.so.2 from the host we also mount its libdrm folder. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Feb 25, 2020
-
-
Simon McVittie authored
Minor fixes for the README file See merge request steam/pressure-vessel!25
-
Simon McVittie authored
Suggested by Ludovico de Nittis on !21. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Assorted pressure-vessel enhancements See merge request steam/pressure-vessel!21
-
- Feb 19, 2020
-
-
Simon McVittie authored
wrap: Remount API filesystems when operating without a runtime See merge request steam/pressure-vessel!23
-
Ludovico de Nittis authored
Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Ludovico de Nittis authored
Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Feb 17, 2020
-
-
Simon McVittie authored
When we start dealing with LD_LIBRARY_PATH runtimes too, the difference will become significant. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Rephrase it so that in the UI, unsharing the home directory looks like the active choice ("separate home directory"), with the shared home directory as the passive/default choice. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
We don't want users who discover this test UI to think that everything is going to work as-is. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
In the case where we bind-mounted the entire root filesystem, since commit 77f3e3d7 we mounted it over the top of API filesystems like /dev, /proc, /sys. This results in /dev being mounted with the nodev option, which breaks a lot of normal functionality like /dev/null. Some games can work despite this, but only badly (Floating Point launches with indirect or software rendering and a horrible framerate), and the xterm activated by PRESSURE_VESSEL_SHELL=instead fails to launch because it can't create a pseudo-terminal. Adjust the order to get this right. Fixes: 77f3e3d7 "wrap: Make sure the intermediate bwrap object can be used as a base" Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Feb 10, 2020
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
-
Simon McVittie authored
It's a little confusing if we run p-v-wrap --test --verbose, which logs: pressure-vessel-wrap: Original argv: ... pressure-vessel-wrap: Checking for bwrap... and then exits. If we add one last line pressure-vessel-wrap: OK (/usr/bin/bwrap) then the result is clearer. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
In some places we said exit status, but meant wait status (the status from waitpid() or similar, which encodes whether the process exited normally, the exit status if yes, the fatal signal if any, and whether a core was dumped). Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Add --test command line argument to pressure-vessel-wrap. See merge request steam/pressure-vessel!19
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This lets us import files from Flatpak that explicitly #include "config.h" as-is, reducing avoidable delta. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Feb 03, 2020
-
-
Jeremy Whiting authored
When --test is used check for bubble wrap executable and return 0 if found, 1 otherwise.
-
- Jan 23, 2020
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Taken from Flatpak. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This syncs us up with how Flatpak does it. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This makes us match how Flatpak includes it, which makes our versions of Flatpak files more similar. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Taken from Flatpak. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This keeps us more in sync with the equivalent code in Flatpak, helping us to merge fixes from there. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jan 08, 2020
-
- Jan 07, 2020
-
-
Simon McVittie authored
wrap: Don't pass --lock-file to bwrap See merge request steam/pressure-vessel!18
-
- Jan 06, 2020
-
-
Simon McVittie authored
Non-OFD locks don't propagate across fork(), and bwrap needs to clone() itself (which behaves like fork() in this respect) to separate itself into a parent outside the container and a child inside the container. This change adds a weak dependency on Linux 3.15. If we run on an older version, everything should still *work*, but there will be a short period of time during which we have already decided to use the runtime, but it is not locked (and in particular not protected from deletion). Fixes: 959fd338 "wrap: Take out a lock on the container's runtime for the duration" Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
These more modern locks, introduced in Linux 3.15 and not yet included in POSIX, propagate across fork(), dup(), fd-passing etc. the way you'd expect: as long as at least one copy of the inherited or fd-passed file descriptor remains open, the lock remains held. This allows us to pass a lock fd to a child process across bwrap's fork-and-exec the way we were already trying to, and have it actually work. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This is redundant with us passing the fd to be held by pressure-vessel-with-lock, and it causes bwrap to produce the wrong exit status (see https://github.com/containers/bubblewrap/issues/336 and https://github.com/containers/bubblewrap/pull/325 ). It should have been removed when the "pass the lock fd" code path was added. Fixes: 959fd338 "wrap: Take out a lock on the container's runtime for the duration" Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Dec 16, 2019
-
-
Simon McVittie authored
Enable AddressSanitizer, UndefinedBehaviourSanitizer See merge request steam/pressure-vessel!14
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>