Skip to content

Add docker compose deploy command #8427

Add docker compose deploy command

Add docker compose deploy command #8427

Triggered via pull request March 18, 2026 21:45
Status Failure
Total duration 11m 48s
Artifacts 30

ci.yml

on: pull_request
bin-image-test  /  prepare
30s
bin-image-test / prepare
Matrix: e2e
Matrix: validate
Matrix: bin-image-test / build
Matrix: binary / build
coverage
0s
coverage
bin-image-test  /  finalize
19s
bin-image-test / finalize
binary  /  finalize
41s
binary / finalize
binary-finalize
20s
binary-finalize
release
8s
release
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 10 warnings
validate (lint)
Process completed with exit code 2.
e2e (plugin, oldstable)
Process completed with exit code 2.
e2e (plugin, stable)
Process completed with exit code 2.
e2e (standalone, stable)
Process completed with exit code 2.
e2e (standalone, oldstable)
Process completed with exit code 2.
validate (validate-headers)
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/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
validate (validate-go-mod)
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/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
validate (validate-docs)
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/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, docker/bake-action@v6, docker/setup-buildx-action@v3, test-summary/action@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
validate (lint)
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/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
e2e (plugin, oldstable)
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/bake-action@v6, docker/setup-buildx-action@v3, test-summary/action@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
e2e (plugin, stable)
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/bake-action@v6, docker/setup-buildx-action@v3, test-summary/action@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
e2e (standalone, stable)
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/bake-action@v6, docker/setup-buildx-action@v3, test-summary/action@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
e2e (standalone, oldstable)
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/bake-action@v6, docker/setup-buildx-action@v3, test-summary/action@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
compose
110 MB
sha256:a784948ad772f829eb0086f920bb4c50938d7520c03015d02c1221078d6a0bda
coverage-data-unit
107 KB
sha256:306295ce178d87ab862e308d07c48dad313b1ab76d915666a9de83095dc63922
docker~compose~2CES99.dockerbuild
67.2 KB
sha256:4a61c727ac8225f75196a0572cf0f2866a08d80230e12afaee36131ef41e170e
docker~compose~7RO21R.dockerbuild
54.8 KB
sha256:a0df242a4fc5dfda1e602cea3f1ec83accc702056fdfc9908cf60f9530d9971f
docker~compose~8YQGJZ.dockerbuild
65.1 KB
sha256:b212c916c68b6c106495149152aab33992d45286bcfca02fc1853a58ea554025
docker~compose~AQMGCJ.dockerbuild
63.7 KB
sha256:914e5ca5f12220a86f21e3bcb32e8da918581045da7697c67421d54d0cee28f5
docker~compose~BWIJHZ.dockerbuild
67.4 KB
sha256:30f9227e67a8618b9c48703350900d9bc2795435e9ede91f9a5bbbaf9de1fd7e
docker~compose~DYJS1K.dockerbuild
54.6 KB
sha256:99773633b2e29f0c7a89199c24eb556d822f10e089af0085af1af075b0c7f883
docker~compose~G93RW1.dockerbuild
69 KB
sha256:1a737527a781fc973c00da3355923359d712221596b1355ceabfd437e34e0a4c
docker~compose~I6JKRV.dockerbuild
68.5 KB
sha256:b70f88df3e339eeb24664bcc4b5e051bb56a65729c45598cd916e94336b752f3
docker~compose~IR3YVS.dockerbuild
54.9 KB
sha256:e4d25966fa7811a418b4cb7ab3aab96bf24b98693d3525c4077c46ded037049b
docker~compose~J4JKPB.dockerbuild
69.9 KB
sha256:76039c0e92762af62de3fd7b5b90c6a68ec428d8cc835cd34724f84a989adf6f
docker~compose~KQPL7G.dockerbuild
63.7 KB
sha256:a34f62eab0dec7f1e6a7c853bf3c70cb2abb2c7b58645ab8d7e63a1fe5ca59fa
docker~compose~L5HDMP.dockerbuild
63.5 KB
sha256:84bc44edc4be31135133823cb8a4f5c14e6903bde45b74adb04edb714bf609ca
docker~compose~LT4W6I.dockerbuild
67.3 KB
sha256:432ba5efb320bb2a9306a424eeba1b5fa6091998ac1b90306b4b515296dc190a
docker~compose~M1AXX6.dockerbuild
64 KB
sha256:714e97deca3ae36dbf2a531f2c4c825cdbfbb95b82ef76bcc4ecf9ac749d22a8
docker~compose~MKONT2.dockerbuild
64.3 KB
sha256:9932eecbbed9ac6cd6c007e3c0dae255fc53b3451dc9e8e0805ce564bc233930
docker~compose~NHD15D.dockerbuild
68.8 KB
sha256:514eb1b2bca6ec45579d8e6d85a5c4e413ba22f41fed83d6c4afb5f4f46f807f
docker~compose~Q2XL12.dockerbuild
64.6 KB
sha256:b8993a8a0abeefe55d79ff99c2f5dc39948c8c97cdc3cfa8b5fbe344d2d10f1f
docker~compose~QIWMP9.dockerbuild
64.6 KB
sha256:cfd2530239f5db9fb76e5e237e23873368cf4bd251c85a8077b34dd55d725b7f
docker~compose~QZ1JIO.dockerbuild
62.9 KB
sha256:245d823a22b65d23e2fdae6582f1f87c1899e2475d494267d75ef3e20e4c0d03
docker~compose~TBGPH5.dockerbuild
68.1 KB
sha256:871ae5b6b3ad60a2528ec0d4ed71d542a40970f7fa93aecba84cd896eaa0b4b4
docker~compose~U24VIY.dockerbuild
64.1 KB
sha256:6b1bcf83256273911c9410bb26982ce1afc9b8d23de2a2762ba2e85b803a6125
docker~compose~UTUXAW.dockerbuild
69.6 KB
sha256:5bb7f5fb4759197b34bb9a35e30184e3df73913a406d89706b1c136a65ae8763
docker~compose~VK01GJ.dockerbuild
67.4 KB
sha256:d8c7c63cde60e6e7877b796cc8961afedb5a005ed22e7cc69c3e69f8399da0ff
docker~compose~WT21ZL.dockerbuild
55.9 KB
sha256:1149cb9d4fe8995355f2878ec3c2943f45318ecc6b00aa2191344a68924f2023
docker~compose~X3QLVH.dockerbuild
65.9 KB
sha256:2e0469b9e96e67f087c8061bd58f6beab16031bcad1c613ae85bc22dc1c5e96f
docker~compose~YI18ZF.dockerbuild
63.5 KB
sha256:4b5e6d37528c2f1f6819aeed8c634c0bf7d75c556e84492b2f4d725128c3b3df
docker~compose~YQAQON.dockerbuild
68.2 KB
sha256:e495d151a86ede915c0ff6a2c06e68b19d3c16c73fcafe30ce9142c80415675c
release
110 MB
sha256:3d87fabbe0e38970f77e273ec604825b0c12c5a42eebca8b459a74c1f7928111