Podman compatibility #205
Merged
Podman compatibility #205
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is needed to restore podman-compose compatibility, since it doesn't support uid and gid options in tmpfs, moreover it's quite silly to have persistent storage on a tmpfs since /data is deleted when the container is stopped. Fixes: 48eccbc ("harden docker-compose") Cc: [email protected]
|
I personally don't use podman, but it doesn't break anything with regular docker so I'll guess it's ok |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I currently use ProxiTok using podman-compose instead of docker as user and it works quite well with just 2 little changes: