Skip to content
Dev-v6 Build & Push

Dev-v6 Build & Push #26

Sign in to view logs

Dev-v6 Build & Push

Dev-v6 Build & Push #26

Triggered via schedule December 12, 2024 11:16
@origamiofficialorigamiofficial
⁠ 30dd63c
main
Status Success
Total duration 2h 42m 48s
Artifacts 1

build-and-push-dev-v6.yaml

on: schedule
Base update check
3s
Base update check
Build and publish
2h 42m
Build and publish
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Base update check
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build and publish
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
The 'as' keyword should match the case of the 'from' keyword: Dockerfile-Dev-V6#L4
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile-Dev-V6#L44
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Legacy key/value format with whitespace separator should not be used: Dockerfile-Dev-V6#L148
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: Dockerfile-Dev-V6#L149
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
origamiofficial~docker-pihole-unbound~SM95JW.dockerbuild
3.7 MB