-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
podman compose
does not find compose providers not in PATH
#20502
Comments
Thanks for reaching out, @xduugu! |
Do not error out immediately but collect all errors and report them if no candidate succeeded. That'll fix containers#20502 and improve the quality of reported errors. [NO NEW TESTS NEEDED] Fixes: containers#20502 Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
Do not error out immediately but collect all errors and report them if no candidate succeeded. That'll fix containers#20502 and improve the quality of reported errors. [NO NEW TESTS NEEDED] Fixes: containers#20502 Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
@vrothberg Thanks for the quick fix! Only the debug message could be improved:
Line 97 in 4871182
|
Nice catch, @xduugu. Are you interested in opening a Pull Request? |
@vrothberg I've opened a pull request #20565 |
Issue Description
If you place the
docker-compose
binary into a directory that is not in your PATH, e.g.$HOME/.docker/cli-plugins/
, which is, according to the default configuration, a supported location,podman compose
only returns the errorSteps to reproduce the issue
Steps to reproduce the issue
docker-compose
binary into one of the supported docker cli-plugins directoriespodman compose
Describe the results you received
podman prints the error message:
Describe the results you expected
podman compose
should finddocker-compose
as compose provider and run it.podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
The error returned by
podman/cmd/podman/compose.go
Line 89 in e5101b2
Is apparently not an
os.ErrNotExist
error, so that all the other candidates are not even tried.podman/cmd/podman/compose.go
Lines 91 to 93 in e5101b2
It is probably sufficient to remove this check and simply always
continue
in case of an error.The text was updated successfully, but these errors were encountered: