chore(deps): bump form-data from 4.0.5 to 4.0.6 in /frontend (#823) #543
RyanYenschAnnotations
7 warnings
|
Build (backend)
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:
backend.dockerfile#L26
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:
backend.dockerfile#L16
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:
backend.dockerfile#L1
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
Build (frontend)
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:
frontend.dockerfile#L64
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:
frontend.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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
devsoc-unsw~freerooms~5CYHA7.dockerbuild
|
58.8 KB |
sha256:70a9e3c299fc895f43b8fe7b3c5a4b74fd7d0778ba63e31a287873319ac5461c
|
|
|
devsoc-unsw~freerooms~PLXVYP.dockerbuild
|
47.5 KB |
sha256:4293c4e1debfd3245df4204d2992acc0998e30b03ea0b673c1f56e2144778fe5
|
|