Closed olichtne closed 1 year ago
This has already been fixed in containers/podman-py#265, but it hasn't been released yet, shouldn't we just wait?
well the don't really seem to have a regular release schedule. I'd rather have a functional CI and then remove this once the update is in place, whenever that may happen. What do you think?
Could you check if this integrates well in our downstream deployment?
scheduled some internal tests: J:7862897
and J:7862902
tests finished fine, merging.
Description
Should fix issues with docker-python we see in CI.
https://github.com/docker/docker-py/issues/3113
Tests
CI tests are enough.
Reviews
(Please add a list of reviewers that should check the validity and sanity of this merge request before it's accepted. Use the
@username
syntax. If you don't know who to mention just link@all
.)Closes: #