Flatpak - Persist Data Written to Arbitrary Locations
If I've understood the Flatpak docs (sandbox permissions and flatpak-override) correctly, the sandbox uses a tempfs and only bind mounts specific directories into it. In particular, my current understanding is that the entire contents of ~/ is not mapped to ~/.var/app/<app-id>/ but rather that individual subdirectories must be mapped on a case by case basis. If true, this would mean that an app unexpectedly writing data to an unmapped subdirectory of ~/ would result in data loss. Unfortunately I don't see an easy way to test this behavior without creating my own Flatpak package.
Is my understanding correct?
Additionally, what would be the easiest way to persist an entire sandboxed home directory at a custom location?
- That is, how might I sandbox the entirety of
~/such that writing to arbitrary subdirectories worked as expected, and map it to a location on an external disk (mounted at/mnt/<disk-id>) instead of~/.var/app/<app-id/. - I know that I can grant access to arbitrary locations via
--filesystem=<path>and that I can map individual subdirectories under~/into the sandbox via--persist=<path>. However, neither of these options would appear to satisfy this use case.
flatpak
asked 29 mins ago
AnOccasionalCashewAnOccasionalCashew
1011
New contributor
AnOccasionalCashew is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
If I've understood the Flatpak docs (sandbox permissions and flatpak-override) correctly, the sandbox uses a tempfs and only bind mounts specific directories into it. In particular, my current understanding is that the entire contents of ~/ is not mapped to ~/.var/app/<app-id>/ but rather that individual subdirectories must be mapped on a case by case basis. If true, this would mean that an app unexpectedly writing data to an unmapped subdirectory of ~/ would result in data loss. Unfortunately I don't see an easy way to test this behavior without creating my own Flatpak package.
Is my understanding correct?
Additionally, what would be the easiest way to persist an entire sandboxed home directory at a custom location?
- That is, how might I sandbox the entirety of
~/such that writing to arbitrary subdirectories worked as expected, and map it to a location on an external disk (mounted at/mnt/<disk-id>) instead of~/.var/app/<app-id/. - I know that I can grant access to arbitrary locations via
--filesystem=<path>and that I can map individual subdirectories under~/into the sandbox via--persist=<path>. However, neither of these options would appear to satisfy this use case.
flatpak
asked 29 mins ago
AnOccasionalCashewAnOccasionalCashew
1011
New contributor
AnOccasionalCashew is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
If I've understood the Flatpak docs (sandbox permissions and flatpak-override) correctly, the sandbox uses a tempfs and only bind mounts specific directories into it. In particular, my current understanding is that the entire contents of ~/ is not mapped to ~/.var/app/<app-id>/ but rather that individual subdirectories must be mapped on a case by case basis. If true, this would mean that an app unexpectedly writing data to an unmapped subdirectory of ~/ would result in data loss. Unfortunately I don't see an easy way to test this behavior without creating my own Flatpak package.
Is my understanding correct?
Additionally, what would be the easiest way to persist an entire sandboxed home directory at a custom location?
- That is, how might I sandbox the entirety of
~/such that writing to arbitrary subdirectories worked as expected, and map it to a location on an external disk (mounted at/mnt/<disk-id>) instead of~/.var/app/<app-id/. - I know that I can grant access to arbitrary locations via
--filesystem=<path>and that I can map individual subdirectories under~/into the sandbox via--persist=<path>. However, neither of these options would appear to satisfy this use case.
flatpak
asked 29 mins ago
AnOccasionalCashewAnOccasionalCashew
1011
New contributor
AnOccasionalCashew is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
If I've understood the Flatpak docs (sandbox permissions and flatpak-override) correctly, the sandbox uses a tempfs and only bind mounts specific directories into it. In particular, my current understanding is that the entire contents of ~/ is not mapped to ~/.var/app/<app-id>/ but rather that individual subdirectories must be mapped on a case by case basis. If true, this would mean that an app unexpectedly writing data to an unmapped subdirectory of ~/ would result in data loss. Unfortunately I don't see an easy way to test this behavior without creating my own Flatpak package.
Is my understanding correct?
Additionally, what would be the easiest way to persist an entire sandboxed home directory at a custom location?
- That is, how might I sandbox the entirety of
~/such that writing to arbitrary subdirectories worked as expected, and map it to a location on an external disk (mounted at/mnt/<disk-id>) instead of~/.var/app/<app-id/. - I know that I can grant access to arbitrary locations via
--filesystem=<path>and that I can map individual subdirectories under~/into the sandbox via--persist=<path>. However, neither of these options would appear to satisfy this use case.
flatpak
flatpak
asked 29 mins ago
AnOccasionalCashewAnOccasionalCashew
1011
New contributor
AnOccasionalCashew is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 29 mins ago
AnOccasionalCashewAnOccasionalCashew
1011
New contributor
AnOccasionalCashew is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 29 mins ago
AnOccasionalCashewAnOccasionalCashew
1011
New contributor
AnOccasionalCashew is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 29 mins ago
AnOccasionalCashewAnOccasionalCashew
1011
asked 29 mins ago
AnOccasionalCashewAnOccasionalCashew
1011
1011
New contributor
AnOccasionalCashew is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
AnOccasionalCashew is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
AnOccasionalCashew is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
AnOccasionalCashew is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f502434%2fflatpak-persist-data-written-to-arbitrary-locations%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
AnOccasionalCashew is a new contributor. Be nice, and check out our Code of Conduct.
AnOccasionalCashew is a new contributor. Be nice, and check out our Code of Conduct.
AnOccasionalCashew is a new contributor. Be nice, and check out our Code of Conduct.
AnOccasionalCashew is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f502434%2fflatpak-persist-data-written-to-arbitrary-locations%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
