-
Notifications
You must be signed in to change notification settings - Fork 365
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
Don't panic if docker version cannot be parsed #298
Comments
Can you submit a PR? |
Sure |
Would be nice to have official/direct support for podman, it's the simplest solution for running containers rootless, daemonless and safely (without being part of high privileged user groups). I suppose that to use it now one has to provide a docker command that redirects to podman, but still not working due to this issue. |
It's not that easy unfortunately. That's why I haven't submitted a patch yet. #!/bin/sh
if [ "$1" == "version" ] && [ "$2" == "--format={{.Server.APIVersion}}" ]; then
echo "100.0"
else
echo "Executing $@"
/usr/bin/podman "$@"
fi On my fedora system SELinux restricts the container to a degree that nothing works. Disabling SELinux fails with a user-id mapping. The docker daemon does work different than podman in this situation. |
It works on ArchLinux, but needs some fixes. First, your wrapper worked for the image to be pulled, but then what
So I executed the command manually with a few edits and the project built:
|
This is my subgid/subuid setup for rootless podman:
|
I think we could just bump the requirement and assume that Docker supports the |
Fixed by #344. |
I'm using podman instead of Docker (podman has a docker cli interface).
But podman, because it works daemonless, correctly reports no "Server API Version":
A less intrusive version check that just warns would work as well, wouldn't it?
See
https://github.com/rust-embedded/cross/blob/e1470782db43fc737cf9b7f14748331228b8229d/src/docker.rs#L26
Thanks
The text was updated successfully, but these errors were encountered: