Open Mgrsc opened 1 week ago
Seems like the relative path is used after the working directory is changed. Interestingly, there is a "TODO Remove" comment above the directory change in line 1815.
An alternative to deleting the line (maybe there is a reason why it wasn't removed) is making the filenames absolute:
@@ -1790,6 +1790,7 @@ class PodmanCompose:
sys.exit(1)
# make absolute
relative_files = files
+ files = [os.path.realpath(filename) for filename in files]
filename = files[0]
project_name = args.project_name
# no_ansi = args.no_ansi
This works on my machine™.
run into same bug today
steps to reproduce:
echo -e "services:\n a:\n image: hello-world" > c.yml
podman-compose -f c.yml up #works
mkdir subdir
mv c.yml subdir/
podman-compose -f subdir/c.yml up #fails
removing https://github.com/containers/podman-compose/blob/main/podman_compose.py#L1818 fixes the issue
I can confirm that with v1.1.0
it works, and the line is present there
https://github.com/containers/podman-compose/blob/v1.1.0/podman_compose.py#L1685
and has been there long time before
so it seems to be introduced by something else between v1.1.0
and v1.2.0
Describe the bug In version 1.2.0, I encountered an error while using 'podman-compose -f lobe/compose.yaml pull', but it worked fine in version 1.1.0. Using the absolute path works normally, but using the relative path results in an error.
To Reproduce
Expected behavior nomal pull
Actual behavior What is the behavior you actually got and that should not happen.
Output