Conversation
Docker 29 broke the integration tests on GitHub Actions. It seems the switch to the containerd image store meant we were trying to mount one overlayfs on top of another which Linux does not currently support. Fixed by moving to the VFS storage driver. This requires more storage so we also need to switch the docker data root to run from /mnt/docker.
VFS creates a separate copy for each layer, so the fewer the better.
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
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.
Docker 29 broke the integration tests on GitHub Actions. It seems the switch to the containerd image store meant we were trying to mount one overlayfs on top of another which Linux does not currently support.
Fixed by moving to the VFS storage driver. This requires more storage so we also need to switch the docker data root to run from /mnt/docker.
This has made the tests a fair bit slower as each docker layer is not a full copy. To mitigate that the number of layers in the docker builds has been optimized.