-
Notifications
You must be signed in to change notification settings - Fork 3.3k
[Ubuntu] Breaking change : Docker Engine Version 26.* will be updated to Docker Engine Version 28* from 2025-05-09 #11766
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
Comments
Related to actions#11766 --- For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/actions/runner-images/issues/11766?shareId=XXXX-XXXX-XXXX-XXXX).
|
Fixes actions#11766 Update Docker Engine to Version 28.* in Ubuntu OS images. * **Update toolset files** - Update `images/ubuntu/toolsets/toolset-2004.json` to list Docker Engine Version 28.*, Docker CE CLI Version 28.*, and Docker Compose Version 2.28.0. - Update `images/ubuntu/toolsets/toolset-2204.json` to list Docker Engine Version 28.*, Docker CE CLI Version 28.*, and Docker Compose Version 2.28.0. - Update `images/ubuntu/toolsets/toolset-2404.json` to list Docker Engine Version 28.*, Docker CE CLI Version 28.*, and Docker Compose Version 2.28.0. * **Add tests for Docker Engine Version 28.*** - Add `images/ubuntu/scripts/tests/Docker.Tests.ps1` to include tests for Docker Engine Version 28.*. --- For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/actions/runner-images/issues/11766?shareId=XXXX-XXXX-XXXX-XXXX).
|
It's great to see the upgrade to Docker Engine v28 is in the works! Unfortunately, it looks like there might be a short time period where the default actions-runner won't behave as expected. Warning This will impact users after April 15, 2025 (when cache v2 becomes the default), and before Docker Engine v28 is available by default in the GitHub-hosted runner images. Working scenarios
Breaking scenarios
Recommended Workaround (Until Runner Images Are Updated)Use the following setup to ensure your workflow uses a compatible Buildx + BuildKit combo: -
name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
with:
version: latest This defaults to the docker-container driver with the latest versions of Buildx and BuildKit. If you're using -
name: Set up Docker Compose
uses: docker/setup-compose-action@v1
with:
version: latest Compatibility Table
|
I am experiencing a ci failure which seems to be a result of this, between ubuntu-22.04 changing from The full CI script is at: And I am using these three actions, basically:
The 0323 image finishes with at the post run actions/cache stage:
While the 0330 image fails to create the cache:
Should I insert the buildx action in the middle or something? Or should I do something after the |
Sorry for the noise. Apparently the correct way to handle |
## Description Note about sunset of GitHub Cache service v1 on April 15th, 2025. ## Related issues or tickets * https://gh.io/gha-cache-sunset * docker/build-push-action#1345 * docker/setup-buildx-action#414 * moby/buildkit#5896 * actions/runner-images#11766 (comment) ## Reviews <!-- Notes for reviewers here --> <!-- List applicable reviews (optionally @tag reviewers) --> - [x] Technical review - [x] Editorial review - [ ] Product review Signed-off-by: CrazyMax <[email protected]>
Note about sunset of GHA cache service v1 added to our docs: https://docs.docker.com/build/ci/github-actions/cache/#github-cache |
I think it's good because we had issues with docker engine version 26.x in gh runners during quarkus based images' builds due to problems with files' timestamps, I think this is fixed in docker engine 28.x what should help. |
Good update |
Breaking changes
Docker Engine Version 26.* will be removed from Ubuntu Os'es and Docker Engine Version 28* will added
Target date
Image deployment will start on 2025-05-05 and will take 2-3 days
The motivation for the changes
Updating the Docker Engine to Latest version i.e 28*, Customers will be able to use the latest version.
Possible impact
If your projects depend on Docker Engine version i.e 26.* they might be broken
Platforms affected
Runner images affected
Mitigation ways
Customers should be able to use the latest version Docker Engine i.e 28.*
N/A
The text was updated successfully, but these errors were encountered: