Fixed Docker 29.0.0 compatibility issue caused by outdated docker client#21
Merged
Conversation
|
@dariuszz123 Can you please resolve the logrus related merge conflict. |
Contributor
Author
|
Conflict resolved. |
Owner
|
build is failing because the CI jobs are still using older go versions |
Contributor
Author
|
Fixed failing workflows by using correct go version. |
|
@costela Any chance you can merge this? |
Owner
|
sorry for the delay and thanks for the contribution! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #20
The old deprecated
docker.io/go-dockerused Docker API version 1.33, which is no longer supported in Docker 29.0.0 (minimum 1.44).This replaces
docker.io/go-dockerwith latest version ofgithub.com/docker/docker, which supports newer API versions.I'm not a Go developer, so please review the changes carefully to ensure everything follows best practices :)