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

for cisagov/Malcolm#780, first stab at integrating vadr dashboards #1001

Sign in to view logs

for cisagov/Malcolm#780, first stab at integrating vadr dashboards

for cisagov/Malcolm#780, first stab at integrating vadr dashboards #1001

Triggered via push September 22, 2025 22:44
@mmguerommguero
pushed e96772f
main
Status Cancelled
Total duration 13m 42s
Artifacts 1

dashboards-build-and-push-ghcr.yml

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

Annotations

4 errors and 10 warnings
docker / docker (ubuntu-24.04-arm, arm64, linux/arm64)
The operation was canceled.
docker / docker (ubuntu-24.04-arm, arm64, linux/arm64)
The run was canceled by @github-actions[bot].
dashboards-build-and-push-ghcr
The run was canceled by @github-actions[bot].
dashboards-build-and-push-ghcr
The run was canceled by @github-actions[bot].
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/
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#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#L23
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#L17
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#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#L82
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~AB8NM2.dockerbuild Expired
60 KB
sha256:282ba3da414c51d2f63543dfa4bfa14ddbe33882ac9ca23178841c4924bf8012