-
Notifications
You must be signed in to change notification settings - Fork 17
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
CI: example image docker build failures #6
Comments
Ummm that's strange |
It doesn't seem like reverting back to |
Okay, it looks like containerd-wasm-shims hit the same issue; https://github.com/deislabs/containerd-wasm-shims/actions/runs/7763088430/job/21174661154?pr=204 |
The difference between the successful run and unsuccessful run: containerd: 1.6.27 -> 1.6.28 |
Related discussion: https://cloud-native.slack.com/archives/C04LTPB6Z0V/p1706919571842939 |
The solution is to enable containerd image store. See #9 |
👏 Thanks @Mossaka! |
The docker build step for example images are failing (when in 'test' mode). See https://github.com/spinkube/containerd-shim-spin/actions/runs/7759094517/job/21162393271?pr=2 and https://github.com/spinkube/containerd-shim-spin/actions/runs/7759094517/job/21162393801?pr=2
Error snippet:
It almost seems like we'd need to switch the
docker/build-push-action
version back tov3
as we do when not in 'test' mode (https://github.com/spinkube/containerd-shim-spin/blob/main/.github/workflows/docker-build-push.yaml#L54-L56).However, the corresponding workflow in deislabs/containerd-wasm-shims doesn't appear to hit the same error, so I'm confused (see for example https://github.com/deislabs/containerd-wasm-shims/actions/runs/7632914430/job/20794094653)
cc @Mossaka
The text was updated successfully, but these errors were encountered: