Docker Image CI #158
docker-image-prod.yml
on: push
Matrix: build-prod-lite / build
Matrix: build-prod / build
build-prod-lite
/
merge
build-prod
/
merge
0s
Annotations
4 errors and 4 warnings
|
build-prod-lite / Build linux/amd64
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c bun --bun vite build --config lite.vite.config.ts" did not complete successfully: exit code: 1
|
|
build-prod / Build linux/arm64
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c bun --bun vite build" did not complete successfully: exit code: 1
|
|
build-prod-lite / Build linux/arm64
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c bun --bun vite build --config lite.vite.config.ts" did not complete successfully: exit code: 1
|
|
build-prod / Build linux/amd64
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c bun --bun vite build" did not complete successfully: exit code: 1
|
|
build-prod-lite / Build linux/amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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-prod / Build linux/arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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-prod-lite / Build linux/arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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-prod / Build linux/amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 | |
|---|---|---|---|
|
yusing~godoxy-webui~LRKI9B.dockerbuild
Expired
|
34.9 KB |
sha256:336cac53d06b52511b76cd819a1b5fd4e4b905087b87c72326f5a3ed02a96236
|
|
|
yusing~godoxy-webui~N1WTVX.dockerbuild
Expired
|
40.2 KB |
sha256:4f90412e94298ab766f88d950160cbbf09d1091a5fdc2d8723ee5d4d0f8bcd38
|
|
|
yusing~godoxy-webui~PTZ7EX.dockerbuild
Expired
|
40.4 KB |
sha256:3bde6a88c6f26d07e0752f618bb28137ad44d1d78ce32a573197a0986c734a20
|
|
|
yusing~godoxy-webui~ZDM40G.dockerbuild
Expired
|
35.4 KB |
sha256:77ebbf823ed52bce71b2cd528aa4b1f6138d50198a7c9195607c0d07ab6f9c8e
|
|