Skip to content

Support GCP-spicific TPU and DeepLearning-VM with AnyCall #227

Support GCP-spicific TPU and DeepLearning-VM with AnyCall

Support GCP-spicific TPU and DeepLearning-VM with AnyCall #227

Triggered via push October 31, 2024 23:38
Status Success
Total duration 6m 26s
Artifacts 1
Publish a container image
6m 18s
Publish a container image
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Legacy key/value format with whitespace separator should not be used: Dockerfile#L56
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: Dockerfile#L29
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: Dockerfile#L8
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#L54
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#L55
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
cloud-barista~cb-spider~IJRR7F.dockerbuild
93.7 KB