<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div>Many many thanks for this information!<br></div><div dir="auto"><br></div><div dir="auto">By making use of $XDG_DATA_HOME I found a workaround.<br></div><div dir="auto"><br></div><div dir="auto">Cheers,<br></div><div style="16px">Olof <br></div><div><br></div><div>31 Jan 2022, 21:59 by b@bpiotrowski.pl:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>On 31/01/2022 21.40, Olof Nord wrote:<br></div><blockquote><div>Hello Flatpak devs!<br></div><div><br></div><div>I have a demo application[1], which during initial startup, extracts some archives inside the Flatpak.<br></div><div><br></div><div>Is there any flags/ways of giving the application write access to its own internal file system?<br></div><div>In my case to "/app/bin/resources".<br></div><div>This folder does not exist during build, but is created at startup.<br></div><div><br></div><div>Currently, I receive the following error message during startup:<br></div><div>"unlinkat /app/bin/resources: read-only file system".<br></div><div><br></div><div>The files are only relevant to the application itself, there is no need to access them from outside.<br></div><div><br></div><div>I have found "--sandbox-expose" to expose read-write access to a file, but this argument isn't valid as a finish-args, and using "--filesystem" isn't really applicable as the folder exists only inside the Flatpak itself (It also does not address the problem, I have tried).<br></div><div><br></div><div>Using Flatpak 1.12.4, flatpak-builder 1.2.2.<br></div><div><br></div><div>Any advice or further information would be greatly appreciated!<br></div><div><br></div><div>Cheers,<br></div><div>Olof Nord<br></div><div><br></div><div>[1]https://gitlab.com/olof-nord/go-astilectron-flatpak-demo <https://gitlab.com/olof-nord/go-astilectron-flatpak-demo><br></div></blockquote><div><br></div><div>As far as I know, /app is read-only except for the extra-data modules, which can extract data to /app/extra during installation. There is no solution to that, it's by design.<br></div><div><br></div><div>A possible workaround is extracting files to $XDG_DATA_HOME, but I assume you would need to change your app to look for the data there.<br></div><div><br></div><div>Bart<br></div></blockquote><div dir="auto"><br></div> </body>
</html>