Skip to content

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

Merge pull request #12 from maxamillion/container-builds

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

Triggered via push April 3, 2026 19:44
Status Failure
Total duration 4m 24s
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

4 errors and 4 warnings
Build gateway (arm64)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c . cross-build.sh && cargo_cross_build --release -p openshell-server -p openshell-sandbox" did not complete successfully: exit code: 101
Build cluster (arm64)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c . cross-build.sh && cargo_cross_build --release -p openshell-server -p openshell-sandbox" did not complete successfully: exit code: 101
Build gateway (amd64)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c . cross-build.sh && cargo_cross_build --release -p openshell-server -p openshell-sandbox" did not complete successfully: exit code: 101
Build cluster (amd64)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c . cross-build.sh && cargo_cross_build --release -p openshell-server -p openshell-sandbox" did not complete successfully: exit code: 101
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 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 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 (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~FZ8QBH.dockerbuild
114 KB
sha256:77074e9cd0f6ad0d257435bcf24c6daf2d29e1a7201f26c568eb64191afdc4b2
LobsterTrap~OpenShell~IV3JZS.dockerbuild
101 KB
sha256:89ad57783d0e90474d55ea7435b8686825f6a8570dbe07064c65e8c904541920
LobsterTrap~OpenShell~OZ4ANA.dockerbuild
110 KB
sha256:a5895cb39ab6e86aa63562a1b025d831b4536433918dc93f7abd8061c0f48b6a
LobsterTrap~OpenShell~YGZBYI.dockerbuild
97.2 KB
sha256:1db71636f42778ff71769160e7b5c9bb4ca6a281cb2b0d5b18f9d15d3788b69a