Skip to content

Deploy

Deploy #302

Triggered via schedule October 6, 2025 00:13
Status Success
Total duration 1m 31s
Artifacts 5

deploy.yml

on: schedule
Matrix: deploy
Fit to window
Zoom out
Zoom in

Annotations

20 warnings
deploy (python3.10, 3.10)
The README content exceeds DockerHub's limit and has been truncated to 25000 bytes.
Legacy key/value format with whitespace separator should not be used: docker-images/python3.10.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: docker-images/python3.10.dockerfile#L13
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: docker-images/python3.10.dockerfile#L11
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/
deploy (python3.11, 3.11)
The README content exceeds DockerHub's limit and has been truncated to 25000 bytes.
Legacy key/value format with whitespace separator should not be used: docker-images/python3.11.dockerfile#L13
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: docker-images/python3.11.dockerfile#L11
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: docker-images/python3.11.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/
deploy (python3.9, 3.9)
The README content exceeds DockerHub's limit and has been truncated to 25000 bytes.
Legacy key/value format with whitespace separator should not be used: docker-images/python3.9.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: docker-images/python3.9.dockerfile#L13
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: docker-images/python3.9.dockerfile#L11
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/
deploy (python3.12, 3.12)
The README content exceeds DockerHub's limit and has been truncated to 25000 bytes.
Legacy key/value format with whitespace separator should not be used: docker-images/python3.12.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: docker-images/python3.12.dockerfile#L13
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: docker-images/python3.12.dockerfile#L11
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/
deploy (latest, 3.12)
The README content exceeds DockerHub's limit and has been truncated to 25000 bytes.
Legacy key/value format with whitespace separator should not be used: docker-images/python3.12.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: docker-images/python3.12.dockerfile#L13
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: docker-images/python3.12.dockerfile#L11
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
tiangolo~uwsgi-nginx-flask-docker~96WJOP.dockerbuild
134 KB
sha256:951147c34ccb6eee1e10b8e1bb0aae6f3657ad55df6c1e2849e6d0c59bf6e4f8
tiangolo~uwsgi-nginx-flask-docker~FVEOTB.dockerbuild
134 KB
sha256:a2fd46b813ee25ff6da2ac1be985283b87ba059e6456df523bc1e618c7b2b581
tiangolo~uwsgi-nginx-flask-docker~KFROKK.dockerbuild
135 KB
sha256:bd95f1f2ab123538b105bcdd0db5e9c8d1fadc9675ca669aa05db725c4004a88
tiangolo~uwsgi-nginx-flask-docker~QNKXON.dockerbuild
134 KB
sha256:704c7082de2a40ea4066c26bedbcfcd11aef22ba09903634155b4f123e7ae33f
tiangolo~uwsgi-nginx-flask-docker~ZGFQHM.dockerbuild
134 KB
sha256:36d9e8016e8381017ee4f5f4fccbccd999a20e4b601c0a3de811e72aa47b49f1