-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Update Docker to 29.1.1 #27995
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
base: master
Are you sure you want to change the base?
Update Docker to 29.1.1 #27995
Conversation
|
Just a couple of things, and the CI is complaining too. But thanks for the work! |
utils/containerd/Makefile
Outdated
| PKG_NAME:=containerd | ||
| PKG_VERSION:=1.7.22 | ||
| PKG_VERSION:=2.2.0 | ||
| PKG_RELEASE:=2 |
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.
Oops, we missed resetting this to 1
utils/dockerd/Makefile
Outdated
| PKG_NAME:=dockerd | ||
| PKG_VERSION:=27.3.1 | ||
| PKG_VERSION:=29.1.1 | ||
| PKG_RELEASE:=4 |
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.
We should reset this to 1 also
| PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz | ||
| PKG_GIT_URL:=github.com/moby/moby | ||
| PKG_GIT_REF:=v$(PKG_VERSION) | ||
| PKG_GIT_REF:=docker-v$(PKG_VERSION) |
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.
Why did we add "docker-" here?
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.
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.
oh, I missed that detail, thanks!
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.
Should be in the commit description.
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.
Should be in the commit description.
I have added it to the commit description.
|
|
||
| define Package/containerd/install | ||
| $(INSTALL_DIR) $(1)/usr/bin/ | ||
| $(INSTALL_BIN) $(PKG_INSTALL_DIR)/bin/{ctr,containerd,containerd-stress,containerd-shim,containerd-shim-runc-v1,containerd-shim-runc-v2} $(1)/usr/bin/ |
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.
Are these not available anymore or something?
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.
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.
Docker version 29 is an upcoming major update that will use containerd-shim-runc-v2 by default and deprecate the older containerd-shim-runc-v1. Therefore, removing containerd-shim-runc-v1 is not a "manual" operation, but rather the default state after the Docker upgrade. It is an inevitable result of the transition of container runtime from the old standard to the new standard (from runc v1 to runc v2). The main purpose is to improve performance, security, and support for the OCI standard. You do not need to actively "remove" it; simply upgrading Docker will achieve the switch.
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.
thanks again for the info!
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.
Well, please add this to your commit.
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.
commit
I have added it to the commit.
utils/runc/Makefile
Outdated
| PKG_NAME:=runc | ||
| PKG_VERSION:=1.1.14 | ||
| PKG_VERSION:=1.3.3 | ||
| PKG_RELEASE:=2 |
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.
We should probably reset this to 1 too.
| PKG_GIT_SHORT_COMMIT:=41ca978 # SHA1 used within the docker executables | ||
| PKG_HASH:=65221f1c70feb1bd1562bb1017b586e4528be877656dc16f5be5659fc9b7e522 | ||
| PKG_GIT_SHORT_COMMIT:=9a84135 # SHA1 used within the docker executables | ||
|
|
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.
Hi, please remove this extra newline
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.
removed
|
You need to squash the extra commits. One per package should be enough. And please make sure that each commit start with the "packagename: " prefix (like "docker: ". |
update to v2.2.0, remove containerd-shim and containerd-shim-runc-v1, docker 29.x has removed old containerd shim processes (containerd-shim and containerd-shim-runc-v1).
update docker cli to v29.1.1.
docker version 29.x has an extra "docker-" prefix. add "docker-" prefix to "PKG_GIT_REF".
docker v29.1.1 requires runc v1.3.3.
okay ,revised as requested |
|
It still fails the new strict CI formality test, as you have no space after the prefix in some of commits. |





📦 Package Details
Maintainer: @gerard Ryan
(You can find this by checking the history of the package
Makefile.)Description:
Update all docker packages to 29.1.1
🧪 Run Testing Details
✅ Formalities
If your PR contains a patch:
git am(e.g., subject line, commit description, etc.)
We must try to upstream patches to reduce maintenance burden.