Skip to content

Latest Build & Push #622

Latest Build & Push

Latest Build & Push #622

Triggered via schedule September 14, 2024 00:51
Status Success
Total duration 1m 10s
Artifacts 1

build-and-push.yaml

on: schedule
Base update check
3s
Base update check
Build and publish
51s
Build and publish
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Legacy key/value format with whitespace separator should not be used: Dockerfile#L5
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#L6
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#L6
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "PLEX_Token") 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#L7
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#L7
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "NGROK_Token") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

Artifacts

Produced during runtime
Name Size
origamiofficial~docker-ngrok-plex~1ER190.dockerbuild
136 KB