fix: flatpak creates Podman socket #860
Merged
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.
What does this PR do?
flatpak creates Podman socket if it does not exist
Signed-off-by: Fabrice Flore-Thébault ffloreth@redhat.com
Screenshot/screencast of this PR
What issues does this PR fix or reference?
fix #656
How to test this PR?
On Linux, running Podman Desktop flatpak, when the directory containing the podman socket doesn't exist, Podman Desktop creates the directory and the socket, but doesn't find it.
I could reproduce the issue with:
I could not reproduce the issue while running:
Therefore, I believe flatpak behavior was the source of the problem.
To test: get the
flatpak
build artifact, and run: