Migrate to current Docker version

[MikeMcC399]

What would you like?

Migrate the process to publish Cypress Docker images so that the current Docker version 26.x 27.x can be used.

Why is this needed?

• The currently used version of Docker is determined by the CircleCI machine image ubuntu-2204 ubuntu-2204:2022.10.2. According to Linux Machine Executor Update - 2022 October Q4 Update this image contains Docker 20.10.18.

• It is unclear whether Docker 20.10 is still supported, however the guidance from the Microsoft supporter on Is Docker 20.10 EOL? moby/moby#45104 recommends updating and Mirantis named Dec 10, 2023 as end-of-life. This is also shown on the unofficial End-of-life site. The current Docker version is 26.1 27.0 (see Docker Engine release notes).

Other

• Issue "Push Factory Image" failure checking cypress/factory:4.0.1 #1093 laid incompatibilities open.

  • Breaking changes in https://github.com/docker/buildx caused a compatibility issue with the 4 year old [email protected] from the https://github.com/cypress-io/docker-image-not-found repo.

  • docker-image-not-found is unable to parse the manifest and cannot determine whether a version has been published or not.

See also

• Latest version of docker buildx build creates manifest list with MediaType v1+json docker/buildx#1964
• docker manifest does not work with output from buildx v0.10 docker/buildx#1509

References

• Linux Machine Executor Update - 2022 October Q4 Update
• Docker Engine 20.10.18 release notes
• Linux Machine Executor - 2024 Q2 Update (Including CUDA)
• Docker Engine 26.1 release notes
• Docker buildx releases

[MikeMcC399]

The Docker Engine has now progressed to release 27.0 (first released on June 24, 2024). This would now be the target version.

[MikeMcC399]

• Although the latest Docker Engine released by Docker is currently 27.x, the highest version available in a CircleCI machine image is 26.x. PR chore: update circleci to ubuntu-2204:2024.05.1 (latest) machine image #1163 therefore resolves this issue as far as currently practically possible.