Skip to content

fix: publish data-manager image via CI and point service.json at ghcr… #97

fix: publish data-manager image via CI and point service.json at ghcr…

fix: publish data-manager image via CI and point service.json at ghcr… #97

Triggered via push April 19, 2026 15:38
Status Failure
Total duration 35s
Artifacts 2

docker.yml

on: push
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 3 warnings
build (data-manager, services/data-manager, services/data-manager/Dockerfile)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c apk add --no-cache osmium-tool curl unzip bash bzip2" did not complete successfully: exit code: 1
build (web, ., apps/web/Dockerfile)
The strategy configuration was canceled because "build.data-manager_services_dat" failed
build (web, ., apps/web/Dockerfile)
The operation was canceled.
build (api, ., apps/api/Dockerfile)
The strategy configuration was canceled because "build.data-manager_services_dat" failed
build (data-manager, services/data-manager, services/data-manager/Dockerfile)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (web, ., apps/web/Dockerfile)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (api, ., apps/api/Dockerfile)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
Medformatik~openmapx~SQPUQI.dockerbuild
16.4 KB
sha256:ab0cacdd87822a481108ae18db6dcde7a0c6cf4b595e3d678a6911a7e3de6661
Medformatik~openmapx~YV18WN.dockerbuild
53 KB
sha256:94284f8aa6ba856bc2a56687054ab710ef766debec5fc9bb050ffe6757b61dd8