Skip to content
Snippets Groups Projects
  • Simon McVittie's avatar
    66d41ccd
    runtime: Optionally copy the runtime, and bind-mount the copy · 66d41ccd
    Simon McVittie authored
    
    This is good for two reasons. In a Flatpak runtime, we will not be able
    to do tricks with arbitrary bind-mounts; if we want the host library
    stack, we will have to rewrite the mutable copy of the runtime to
    replace container libraries with symlinks into /run/host. Also, when
    not in a Flatpak runtime, having a mutable copy of the immutable runtime
    gives developers a chance to edit the runtime to inject workarounds or
    things they're testing.
    
    Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>
    66d41ccd
    History
    runtime: Optionally copy the runtime, and bind-mount the copy
    Simon McVittie authored
    
    This is good for two reasons. In a Flatpak runtime, we will not be able
    to do tricks with arbitrary bind-mounts; if we want the host library
    stack, we will have to rewrite the mutable copy of the runtime to
    replace container libraries with symlinks into /run/host. Also, when
    not in a Flatpak runtime, having a mutable copy of the immutable runtime
    gives developers a chance to edit the runtime to inject workarounds or
    things they're testing.
    
    Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>
wrap.c 41.21 KiB