Repository navigation
Fix Vapor deploys failing on the ubuntu-26.04 runner - #1448
Merged
Merged
Conversation
ubuntu-latest moved to 26.04, whose Docker pushes an image index with a provenance attestation. Lambda rejects that, so staging deploys failed at Updating Function Code.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The staging deploy in https://github.com/HiEventsDev/Hi.Events/actions/runs/40200199461 failed at
Updating Function Code:ubuntu-latestmoved from 24.04 to 26.04 between the last green deploy and this one. The newer Docker adds a provenance attestation by default, so the push is an image index (exporting attestation manifest/exporting manifest listin the log) rather than a single image manifest, and Lambda rejects it.ubuntu-24.04.BUILDX_NO_DEFAULT_ATTESTATIONS=1on thevapor deploystep so the image stays a plain manifest when the runner image moves again.The frontend job is unchanged and stays on
ubuntu-latest. It was skipped in the failed run (it needs the backend job), so it has not run on 26.04 yet.Testing: the merge to
developtriggers the staging deploy, which is the check. Production (main) would fail the same way until this lands there.