Create and publish Docker images

Azure: add note about AI Foundry. #757 #1716

Sign in to view logs

Triggered via push February 17, 2025 16:30

enricoros

v2-dev

Status Success

Total duration 22m 44s

Artifacts 1

docker-image.yml

on: push

build-and-push-image

Annotations

6 warnings

build-and-push-image

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

Legacy key/value format with whitespace separator should not be used: Dockerfile#L59

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#L60

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#L3

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#L17

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#L37

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
enricoros~big-AGI~9BCBOD.dockerbuild	87.1 KB