Build and Push Ecommerce Image #4
push-ecommerce-image.yaml
on: schedule
build-and-push-image
30m 49s
Annotations
12 warnings
build-and-push-image
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/
|
build-and-push-image
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/ecommerce.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:
dockerfiles/ecommerce.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:
dockerfiles/ecommerce.Dockerfile#L38
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/ecommerce.Dockerfile#L1
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:
dockerfiles/ecommerce.Dockerfile#L74
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/ecommerce.Dockerfile#L22
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/ecommerce.Dockerfile#L23
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/ecommerce.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/
|
Legacy key/value format with whitespace separator should not be used:
dockerfiles/ecommerce.Dockerfile#L76
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:
dockerfiles/ecommerce.Dockerfile#L91
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/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
edx~public-dockerfiles~80DJI0.dockerbuild
|
223 KB |
|