Skip to content

fix(deps): update ghcr.io/containerbase/base docker tag to v9.20.6 #2187

fix(deps): update ghcr.io/containerbase/base docker tag to v9.20.6

fix(deps): update ghcr.io/containerbase/base docker tag to v9.20.6 #2187

Triggered via push September 28, 2023 18:31
Status Failure
Total duration 1h 30m 4s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

build.yaml

on: push
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 1 warning
build
ExecError: ExecError: (1) Note that if your submission includes personal data associated with this signed artifact, it will be part of an immutable record. This may include the email address associated with the account with which you authenticate your contractual Agreement. This information will be used for signing this artifact and will be stored in public transparency logs and cannot be removed later, and is subject to the Immutable Record notice at https://lfprojects.org/policies/hosted-project-tools-immutable-records/. By typing 'y', you attest that (1) you are not submitting the personal data of any other person; and (2) you understand and agree to the statement and the Agreement terms at the URLs listed above. tlog entry created with index: 39239624 Pushing signature to: index.docker.io/containerbase/node Error: signing [containerbase/node:20.0.0]: recursively signing: signing digest: GET https://auth.docker.io/token?scope=repository%3Acontainerbase%2Fnode%3Apush%2Cpull&service=registry.docker.io: unexpected status code 503 Service Unavailable main.go:74: error during command execution: signing [containerbase/node:20.0.0]: recursively signing: signing digest: GET https://auth.docker.io/token?scope=repository%3Acontainerbase%2Fnode%3Apush%2Cpull&service=registry.docker.io: unexpected status code 503 Service Unavailable
build
ExecError: ExecError: (1) Successfully verified SCT... WARNING: Image reference containerbase/node:20.3.0 uses a tag, not a digest, to identify the image to sign. This can lead you to sign a different image than the intended one. Please use a digest (example.com/ubuntu@sha256:abc123...) rather than tag (example.com/ubuntu:latest) for the input to cosign. The ability to refer to images by tag will be removed in a future release. Error: signing [containerbase/node:20.3.0]: accessing entity: GET https://auth.docker.io/token?scope=repository%3Acontainerbase%2Fnode%3Apull&service=registry.docker.io: unexpected status code 503 Service Unavailable main.go:74: error during command execution: signing [containerbase/node:20.3.0]: accessing entity: GET https://auth.docker.io/token?scope=repository%3Acontainerbase%2Fnode%3Apull&service=registry.docker.io: unexpected status code 503 Service Unavailable
build
ExecError: ExecError: (1) #16 DONE 0.0s #14 exporting to image #14 pushing layers 14.1s done #14 ERROR: failed to push containerbase/node:20.6.0: failed to authorize: failed to fetch oauth token: unexpected status from POST request to https://auth.docker.io/token: 503 Service Unavailable ------ > exporting to image: ------ ERROR: failed to solve: failed to push containerbase/node:20.6.0: failed to authorize: failed to fetch oauth token: unexpected status from POST request to https://auth.docker.io/token: 503 Service Unavailable
build
failed
build
Failed list:20.0.0 20.3.0 20.6.0