[Tech] Bump org.flywaydb:flyway-core from 10.21.0 to 11.1.0 in /backend #116
database.yml
on: push
Matrix: Build database image
Matrix: Build database upgrade image
Annotations
5 errors and 5 warnings
Build database image (11, 2.3.1, 3.3.4, pg11.Dockerfile, pg11-ts2.3.1-postgis3.3.4)
buildx failed with: ERROR: failed to solve: failed to compute cache key: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/timescale/timescaledb/blobs/sha256:86f8340bd3d9f676a8b82d79fa7505af62500227d8991affdbacbdc428fb3c38: 403 Forbidden
|
Build database image (13, 2.14.2, 3.5.1, pg13_16.Dockerfile, pg13-ts2.14.2-postgis3.5.1)
The job was canceled because "_11_2_3_1_3_3_4_pg11_Dock" failed.
|
Build database image (16, 2.14.2, 3.5.1, pg13_16.Dockerfile, pg16-ts2.14.2-postgis3.5.1)
The job was canceled because "_11_2_3_1_3_3_4_pg11_Dock" failed.
|
Build database image (11, 1.7.4, 2.5.5, pg11.Dockerfile, pg11-ts1.7.4-postgis2.5.5)
The job was canceled because "_11_2_3_1_3_3_4_pg11_Dock" failed.
|
Build database image (11, 1.7.4, 2.5.5, pg11.Dockerfile, pg11-ts1.7.4-postgis2.5.5)
The operation was canceled.
|
Default value for global ARG results in an empty or invalid base image name:
infra/docker/database/upgrade_pg.Dockerfile#L7
InvalidDefaultArgInFrom: Default value for ARG postgres:$TO_PG_MAJOR-$DISTRIBUTION results in empty or invalid base image name
More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
|
Legacy key/value format with whitespace separator should not be used:
infra/docker/database/upgrade_pg.Dockerfile#L22
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:
infra/docker/database/upgrade_pg.Dockerfile#L23
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:
infra/docker/database/upgrade_pg.Dockerfile#L25
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:
infra/docker/database/upgrade_pg.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/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
MTES-MCT~monitorfish~NJ0BII.dockerbuild
|
62.5 KB |
|
MTES-MCT~monitorfish~OWYTY0.dockerbuild
|
21.6 KB |
|