podman-compose cannot recognize relative paths correctly #1515
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
TamiTakamiya
commented
Jan 30, 2025
|
TamiTakamiya
deleted the
TamiTakamiya/podman-compose-relative-path-issue
branch
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.
Jira Issue: n/a
Description
podman-compose 1.20 has an issue to recognize relative paths given with
-fparameter. (reference)Since it still can process absolute paths, we'll update our
Makefileto use absolute paths by adding${PWD}in front of relative pathsTesting
Steps to test
podman-compose, likemake start-backends.Scenarios tested
Manually ran
maketargets.Production deployment