Skip to content
Build and Publish Docker Images

chore: initial structure with one image #11

Sign in to view logs

chore: initial structure with one image

chore: initial structure with one image #11

Triggered via pull request October 23, 2024 12:27
@huniafatima-arbihuniafatima-arbi
synchronize #42
huniafatima/unified-workflow-for-image-publish
Status Failure
Total duration 4m 54s
Artifacts 1

push-docker-images.yml

on: pull_request
Matrix: push
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 12 warnings
push (commerce-coordinator, commerce coordinator, linux/arm64, abc, [email protected])
buildx failed with: ERROR: failed to solve: target stage "abc" could not be found
push (course-discovery, course discovery, linux/arm64, dev, [email protected])
The job was canceled because "commerce-coordinator_comm" failed.
push (course-discovery, course discovery, linux/arm64, dev, [email protected])
The operation was canceled.
push (credentials, credentials, linux/arm64, dev, [email protected])
The job was canceled because "commerce-coordinator_comm" failed.
push (credentials, credentials, linux/arm64, dev, [email protected])
The operation was canceled.
push (commerce-coordinator, commerce coordinator, linux/arm64, abc, [email protected])
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/github-script@v5. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
push (commerce-coordinator, commerce coordinator, linux/arm64, abc, [email protected])
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/github-script@v5. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Legacy key/value format with whitespace separator should not be used: dockerfiles/credentials.Dockerfile#L43
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/
The 'as' keyword should match the case of the 'from' keyword: dockerfiles/credentials.Dockerfile#L1
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: dockerfiles/credentials.Dockerfile#L41
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/credentials.Dockerfile#L39
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/credentials.Dockerfile#L40
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/credentials.Dockerfile#L42
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: dockerfiles/credentials.Dockerfile#L43
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "CREDENTIALS_CFG") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: dockerfiles/credentials.Dockerfile#L93
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/
Legacy key/value format with whitespace separator should not be used: dockerfiles/credentials.Dockerfile#L99
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/
The 'as' keyword should match the case of the 'from' keyword: dockerfiles/credentials.Dockerfile#L97
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Artifacts

Produced during runtime
Name Size
edx~public-dockerfiles~ADY1MQ.dockerbuild
8.21 KB