Skip to content
Snippets Groups Projects
  1. Dec 10, 2020
  2. Dec 09, 2020
    • Simon McVittie's avatar
      pressure-vessel: Make graphics drivers outside $HOME available, if used · 23834972
      Simon McVittie authored
      Since !173, we have been able to create symbolic links to graphics
      drivers anywhere on the filesystem, but that didn't mean the graphics
      driver would necessarily be usable, because the directory containing it
      would not necessarily be visible in the container. Add these directories
      to the list of directories to be "exported".
      
      Manual test (Debian on on Intel hardware, adjust as required for
      others):
      
      * Modify /usr/share/vulkan/icd.d/intel_icd.i686.json
        to use /opt/moved-from-usr/lib/i386-linux-gnu/libvulkan_intel.so
      * Move the real i386 libvulkan_intel.so to that location
      * ./run --verbose -- steam-runtime-system-info 2>&1 | tee container.log
      
      Resolves: #29
      Resolves: https://github.com/ValveSoftware/steam-runtime/issues/313
      
      
      Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>
      23834972
  3. Dec 04, 2020
  4. Dec 03, 2020
  5. Nov 30, 2020
  6. Nov 20, 2020
  7. Nov 18, 2020
  8. Nov 17, 2020
  9. Oct 26, 2020
  10. Oct 01, 2020
  11. Sep 29, 2020
  12. Sep 25, 2020
  13. Sep 21, 2020
  14. Sep 09, 2020
  15. Sep 08, 2020
  16. Sep 04, 2020
  17. Sep 03, 2020
  18. Sep 02, 2020
    • Ludovico de Nittis's avatar
      Initial support for custom graphics provider path and Flatpak · d7ad67a2
      Ludovico de Nittis authored
      
      pressure-vessel had a few hard coded assumptions about the host system
      and where to look at for the graphics provider.
      
      For example it was assumed that the root was the same host system used
      by both pressure-vessel current environment (where pressure-vessel-wrap
      runs) and also later on by `bwrap`.
      
      But when we run pressure-vessel in a Flatpak container, the final
      `bwrap` command is expected to be executed against the real host system
      (mounted in `/run/host`, in Flatpak).
      
      Also when we are in a Flatpak container we might want to pick the
      graphics stack from the host system (`/run/host`), from the Flatpak
      container itself or it could even be a completely separate one.
      (T22373, T22371)
      
      Signed-off-by: default avatarLudovico de Nittis <ludovico.denittis@collabora.com>
      d7ad67a2
    • Ludovico de Nittis's avatar
      bwrap: Build arguments to bind /usr if already in a container · f81c2d57
      Ludovico de Nittis authored
      
      The filesystem that is providing /usr might not be mounted
      in the same place in the current namespace, and on the host
      system where bwrap will be run. If it isn't, we need
      to use one path to do file I/O when inspecting it, but pass
      a different path to bwrap.
      
      Signed-off-by: default avatarLudovico de Nittis <ludovico.denittis@collabora.com>
      f81c2d57
  19. Aug 20, 2020
Loading