I'm working on Flatpak Python app, that needs to also interact with some host filesystem elements. While the application is running, another process, running outside of flatpak environment creates new mounts - overlayfs and squashfs mountings. The problem is that flatpack application doesn't detect these mountings until it's restarted, which I cannot do. So it goes like that: 1. Flatpak app client is started 2. Another process mounts overlayfs in some directory 3. Flatpak should be able to access the contents of this mounting with --filesystem=/var/tmp/my_app, and the mount point itself is for example /var/tmp/my_app/random_id, but it doesn't see the contents. Unfortunately when dealing with mounts it does not detect the content's of this new directory. But it is able to access it with no problem after client is started again. I also checked the contents of /proc/mounts reported inside flatpack env, and it doesn't show this new mounting until it is restarted. Interestingly this works fine on Fedora, but I have this issue on Gentoo. I was wondering what components are responsible for this behavior and if there is anything I can do to overcome this. Both Fedora and Gentoo uses the same flatpack version number - 1.16.1. Continue reading...
