Skip to content

Update github workflow #11

Update github workflow

Update github workflow #11

Triggered via push May 31, 2026 15:23
Status Success
Total duration 9m 2s
Artifacts 1

ci.yml

on: push
Build and publish Docker image
8m 28s
Build and publish Docker image
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Build and publish Docker image
Failed to save: Unable to reserve cache with key docker.io--tonistiigi--binfmt-latest-linux-x64, another job may be creating this cache.
Legacy key/value format with whitespace separator should not be used: Dockerfile#L32
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/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L35
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "PAD_SECRET") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L35
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#L34
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#L33
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
dotzero~pad~9EA6G3.dockerbuild
164 KB
sha256:b7e73ef62fa0d5e1ba254be396e7911ae8b47a4f34f822f0d41c87c9b2dda876