Improvements to pressure-vessel handling of LD_PRELOAD
-
wrap: Skip exposing paths that we already binded
-
wrap: Do not add LD_PRELOAD to the container environment
If we don't use
--setenv
directly, the process that we create with "pv_bwrap_execve()" could throw some errors because it is unable to preload the libraries that we specified, because they are valid only in the container structure.
These changes are related to the issue #22 (closed). Now that we are relaunching the container by default steamlinuxruntime!28 (merged), I decided to try the least disruptive, and safer, approach first.
Most of the work outlined in #22 (closed) for the handling, and guessing, of LD_PRELOAD
can be avoided.
Of course if it turns out that the relaunch is something that we shouldn't do, then some more changes to LD_PRELOAD
will be necessary.
But as it is now, we relaunch the container when we reach the main program, so we are able to easily transform the LD_PRELOAD
entries and create a container that binds all the necessary files.