Skip to content

Docker Publish

Docker Publish #1632

Triggered via schedule January 18, 2025 02:21
Status Failure
Total duration 50m 14s
Artifacts 36

docker.yml

on: schedule
Matrix: Build image
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 82 warnings
Build image (php84)
Process completed with exit code 18.
Build image (php81)
Process completed with exit code 1.
Build image (php82)
Process completed with exit code 1.
Build image (php83)
Process completed with exit code 1.
Build image (code)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build image (smb)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build image (nginx)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build image (push)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build image (ldap)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build image (lookupserver)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: docker/lookupserver/Dockerfile#L48
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: docker/lookupserver/Dockerfile#L48
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
Build image (saml)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build image (talk-janus)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build image (codedev)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
FROM --platform flag should not use a constant value: docker/codedev/Dockerfile#L1
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64" More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
FROM --platform flag should not use a constant value: docker/codedev/Dockerfile#L1
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64" More info: https://docs.docker.com/go/dockerfile/rule/from-platform-flag-const-disallowed/
Build image (elasticsearch)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build image (php74)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile.php74#L89
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/Dockerfile.php74#L90
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/Dockerfile.php74#L91
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/Dockerfile.php74#L93
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/Dockerfile.php74#L89
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/Dockerfile.php74#L90
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/Dockerfile.php74#L91
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/Dockerfile.php74#L93
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/
Build image (php72)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile.php72#L89
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/Dockerfile.php72#L90
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/Dockerfile.php72#L91
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/Dockerfile.php72#L93
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/Dockerfile.php72#L89
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/Dockerfile.php72#L90
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/Dockerfile.php72#L91
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/Dockerfile.php72#L93
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/
Build image (php73)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile.php73#L89
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/Dockerfile.php73#L90
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/Dockerfile.php73#L91
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/Dockerfile.php73#L93
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/Dockerfile.php73#L89
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/Dockerfile.php73#L90
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/Dockerfile.php73#L91
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/Dockerfile.php73#L93
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/
Build image (php71)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile.php71#L91
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/Dockerfile.php71#L93
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/Dockerfile.php71#L89
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/Dockerfile.php71#L90
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/Dockerfile.php71#L89
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/Dockerfile.php71#L90
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/Dockerfile.php71#L91
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/Dockerfile.php71#L93
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/
Build image (mailhog)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
The 'as' keyword should match the case of the 'from' keyword: docker/mailhog/Dockerfile#L5
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: docker/mailhog/Dockerfile#L5
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Build image (php80)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile.php80#L91
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/Dockerfile.php80#L93
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/Dockerfile.php80#L89
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/Dockerfile.php80#L90
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/Dockerfile.php80#L90
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/Dockerfile.php80#L91
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/Dockerfile.php80#L93
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/Dockerfile.php80#L89
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/
Build image (php84)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: docker/php84/Dockerfile#L89
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/php84/Dockerfile#L90
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/php84/Dockerfile#L91
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/php84/Dockerfile#L93
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/
Build image (php81)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile.php81#L89
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/Dockerfile.php81#L90
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/Dockerfile.php81#L91
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/Dockerfile.php81#L93
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/
Build image (php82)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: docker/php82/Dockerfile#L91
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/php82/Dockerfile#L93
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/php82/Dockerfile#L89
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/php82/Dockerfile#L90
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/
Build image (php83)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: docker/php83/Dockerfile#L89
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/php83/Dockerfile#L90
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/php83/Dockerfile#L91
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/php83/Dockerfile#L93
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
juliusknorr~nextcloud-docker-dev~1E5KBR.dockerbuild
16.9 KB
juliusknorr~nextcloud-docker-dev~AUL7AS.dockerbuild
102 KB
juliusknorr~nextcloud-docker-dev~C5ZT6T.dockerbuild
104 KB
juliusknorr~nextcloud-docker-dev~E10NPY.dockerbuild
23.5 KB
juliusknorr~nextcloud-docker-dev~E17G0U.dockerbuild
47.2 KB
juliusknorr~nextcloud-docker-dev~E1ZRC9.dockerbuild
107 KB
juliusknorr~nextcloud-docker-dev~GC1KII.dockerbuild
29.2 KB
juliusknorr~nextcloud-docker-dev~H672FU.dockerbuild
237 KB
juliusknorr~nextcloud-docker-dev~HHM84Q.dockerbuild
36.7 KB
juliusknorr~nextcloud-docker-dev~JLQ23Y.dockerbuild
29 KB
juliusknorr~nextcloud-docker-dev~JSLAI2.dockerbuild
427 KB
juliusknorr~nextcloud-docker-dev~KRGDU4.dockerbuild
158 KB
juliusknorr~nextcloud-docker-dev~N0P81Y.dockerbuild
44.6 KB
juliusknorr~nextcloud-docker-dev~NBDPOV.dockerbuild
235 KB
juliusknorr~nextcloud-docker-dev~NO95MU.dockerbuild
91.1 KB
juliusknorr~nextcloud-docker-dev~NU1X2O.dockerbuild
237 KB
juliusknorr~nextcloud-docker-dev~O3OM8P.dockerbuild
45.6 KB
juliusknorr~nextcloud-docker-dev~O5RJJ7.dockerbuild
242 KB
juliusknorr~nextcloud-docker-dev~ODXTAZ.dockerbuild
96.9 KB
juliusknorr~nextcloud-docker-dev~OTLRYA.dockerbuild
104 KB
juliusknorr~nextcloud-docker-dev~OUOESK.dockerbuild
239 KB
juliusknorr~nextcloud-docker-dev~P4HDV1.dockerbuild
35.4 KB
juliusknorr~nextcloud-docker-dev~PWT7W6.dockerbuild
71.7 KB
juliusknorr~nextcloud-docker-dev~QGWQ5X.dockerbuild
14.5 KB
juliusknorr~nextcloud-docker-dev~QIGPQR.dockerbuild
45 KB
juliusknorr~nextcloud-docker-dev~R79YF4.dockerbuild
29.1 KB
juliusknorr~nextcloud-docker-dev~SBZTXK.dockerbuild
104 KB
juliusknorr~nextcloud-docker-dev~UBGQEI.dockerbuild
18.4 KB
juliusknorr~nextcloud-docker-dev~ULXLTZ.dockerbuild
39.4 KB
juliusknorr~nextcloud-docker-dev~UQ2UGE.dockerbuild
744 KB
juliusknorr~nextcloud-docker-dev~WI9WR5.dockerbuild
30.5 KB
juliusknorr~nextcloud-docker-dev~WQ0AH1.dockerbuild
429 KB
juliusknorr~nextcloud-docker-dev~X2UPE0.dockerbuild
175 KB
juliusknorr~nextcloud-docker-dev~XP78CQ.dockerbuild
70.7 KB
juliusknorr~nextcloud-docker-dev~YE65MH.dockerbuild
994 KB
juliusknorr~nextcloud-docker-dev~YSB4UA.dockerbuild
44.5 KB