v0.0.19 #21
Triggered via release
December 17, 2024 11:07
matoushavlena
released
v0.0.19
Status
Success
Total duration
1h 4m 36s
Artifacts
1
publish-release-image.yml
on: release
build-and-push
1h 4m
Annotations
6 warnings
build-and-push
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Legacy key/value format with whitespace separator should not be used:
Dockerfile#L73
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/
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
Dockerfile#L77
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
Sensitive data should not be used in the ARG or ENV commands:
Dockerfile#L40
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "AUTH_JWKS_ENDPOINT")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
Sensitive data should not be used in the ARG or ENV commands:
Dockerfile#L41
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "DUMMY_JWT_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#L51
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 | |
---|---|---|
i-am-bee~bee-ui~CM97J9.dockerbuild
|
149 KB |
|