Skip to content

Merge pull request #13 from maxamillion/container-builds #15

Merge pull request #13 from maxamillion/container-builds

Merge pull request #13 from maxamillion/container-builds #15

Triggered via push April 3, 2026 20:17
Status Failure
Total duration 12m 3s
Artifacts 4
Matrix: build
Merge gateway manifest
0s
Merge gateway manifest
Merge cluster manifest
0s
Merge cluster manifest
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
Build gateway (arm64)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c mkdir -p /build/crates/openshell-server" did not complete successfully: exit code: 1
Build gateway (amd64)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c mkdir -p /build/crates/openshell-server" did not complete successfully: exit code: 1
Build gateway (arm64)
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/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 gateway (amd64)
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/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 cluster (arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, azure/setup-helm@v4, docker/build-push-action@v6, docker/login-action@v3, 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 cluster (amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, azure/setup-helm@v4, docker/build-push-action@v6, docker/login-action@v3, 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
LobsterTrap~OpenShell~MHSA1K.dockerbuild
96.3 KB
sha256:91d9270d91d3dab74e68d85103c22df84baa372c0985ac089179a0d31beb9c86
LobsterTrap~OpenShell~MXL3I4.dockerbuild
227 KB
sha256:b66553f5c74a57cbcda6aec7d6bd456a17b275fb31b95b1394286d68a1cdf227
LobsterTrap~OpenShell~QCLA86.dockerbuild
210 KB
sha256:a4907b4c0fa83ca588fa53234fc97f86c11653fc4e7fcaac54cb5c1b918b945a
LobsterTrap~OpenShell~UFN5DB.dockerbuild
97.4 KB
sha256:0dff25adaf72f0ee629a926136c80e2180e70bc26f3188e796eafd752e4b8ed8