Trying to add a specific library to container's path via FlatSeal

1

Hi there - I’m trying to see if there’s a way to include a specific directory of libraries to a flatpak container’s internal path.

I’ve tried adding an ENV variable for export (in flatseal) as follows:

PATH=“$HOME/.local/bin/mylib:$PATH”

however, the flatpak will not run when I do this, giving an error like:

bwrap: execvp bitwig-studio: No such file or directory

In my case, what I’m trying to do is see if I can expose the yabridge libraries to the Btiwig Studio flatpak install so that I might be able to use my windows-based vst3s. (FWIW, these work well with Reaper)

I’ve tried absolute paths, single, double, no quotes, etc. But, in the end, I’m not convinced this is the issue.

Is there a workaround that would allow a Flatpak container to access specific binaries as part of its internal path?

Also, FWIW, I’ve tried allowing access to host libraries, etc. with no luck.

Through this, I’m trying to get a better understanding of flatpak inner workings while also proving to myself that a reasonable solution is possible for my needs. (I am aware that the recommendation is to use the deb version of Bitwig and avoid the flatpak if at all possible, but in this exercise, I wanted to try to develop an understanding of why. Besides, it defeats the goal of keeping a relatively maintainable release, since I’d have to convert from deb to rpm…)

Thanks!

2

that’s because env subsitution isn’t done as that level. So the path is literally set to what you set it.

3

I’m not sure I follow. Does this mean I cannot set the $PATH as an environment variable from flatseal, or that if I do, I must make it a literal string of paths (colon separated) (perhaps by grabbing the defaulted paths by entering and inspecting a running container?

I ask because I believe that $PATH is one of the special env vars that are not pulled into a container as it starts for security reasons.