Skip to content
dashboards-build-and-push-ghcr

rename some dashboards #1040

Sign in to view logs

rename some dashboards

rename some dashboards #1040

Triggered via push November 20, 2025 23:48
@mmguerommguero
pushed a201e0b
hedgehog-iso-refactor
Status Failure
Total duration 3m 20s
Artifacts 2

dashboards-build-and-push-ghcr.yml

on: push
Matrix: docker / docker
Fit to window
Zoom out
Zoom in

Annotations

1 error and 11 warnings
docker / docker (ubuntu-24.04-arm, arm64, linux/arm64)
buildx failed with: ERROR: failed to build: failed to solve: failed to load cache key: invalid response status 503
docker / docker (ubuntu-24.04, amd64, linux/amd64)
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
Legacy key/value format with whitespace separator should not be used: Dockerfiles/dashboards.Dockerfile#L15
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfiles/dashboards.Dockerfile#L14
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfiles/dashboards.Dockerfile#L83
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfiles/dashboards.Dockerfile#L81
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfiles/dashboards.Dockerfile#L29
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfiles/dashboards.Dockerfile#L26
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfiles/dashboards.Dockerfile#L24
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfiles/dashboards.Dockerfile#L21
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfiles/dashboards.Dockerfile#L18
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfiles/dashboards.Dockerfile#L16
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Artifacts

Produced during runtime
Name Size Digest
mmguero-dev~Malcolm~IZF3FV.dockerbuild Expired
62.6 KB
sha256:7791e3d310cd498789b1bffaeede4a99bb3dd2c907fb33ae9fcb98137f039087
mmguero-dev~Malcolm~OH5S43.dockerbuild Expired
25.8 KB
sha256:ec256e2647c6ac388e1dd3a72cf66e8da61539a7618753c74e38a87fd1b1e064