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
Docker provider: catch container name when using podman. #11356
Docker provider: catch container name when using podman. #11356
Conversation
LGTM. |
Note: this is using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like how unintrusive it is. Maybe there'll be more changes needed, but I'll test it in Fedora.
577475f
to
a170709
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even better. This allows for any output that has 64-char hashes.
7adf7b6
to
eb30324
Compare
Deleted extra newline. |
When user is using podman's docker CLI emulation the containers would fail to enter running state because the docker driver could not catch the container name. This commit fixes that by adding a check if podman docker emulation is used and pick the container hash correctly from the output.
eb30324
to
5208032
Compare
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
When user is using podman's docker CLI emulation the containers would
fail to enter running state because the docker driver could not catch
the container name. This commit fixes that by adding a check if podman
docker emulation is used and pick the container hash correctly from the
output.