containers / containers/podman-compose
Command line --project-directory missing
Open
enhancement
- Dominant language
- Python
- Stars
- 6.2k
- Forks
- 622
- PR merge metrics
- No merged PRs in 30d
Description
Currently, when running a compose file in a sub-folder, it takes that folder as a basis for all subsequent elements.
Imagine parent with .yaml file in sub-folder and invocating using `podman compose --file=sub/myproject.yaml`
If any folder registered in volume in the form of `../anothersub`, path substitution is converting this to `sub/sub/anothersub` which is clearly an error.
Being able to specify `--project-directory parent` would avoid related issues and enhance docker compatibility.
Contributor guide
Assessment
This issue has not been assessed yet.