Skip to content

dispatch-build

dispatch-build #612

Triggered via repository dispatch March 29, 2026 07:34
@osg-botosg-bot
dispatch-build ae20b9d
Status Failure
Total duration 42m 46s
Artifacts

build-container.yml

on: repository_dispatch
make-date-tag
2s
make-date-tag
Matrix: build
Matrix: dispatch
Fit to window
Zoom out
Zoom in

Annotations

21 errors and 21 warnings
build (hub.opensciencegrid.org/osg-htc/alma10-base:combo, el10, testing, 25)
buildx failed with: ERROR: failed to build: failed to solve: hub.opensciencegrid.org/osg-htc/alma10-base:combo: failed to resolve source metadata for hub.opensciencegrid.org/osg-htc/alma10-base:combo: failed to copy: httpReadSeeker: failed open: failed to do request: Get "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/f3/f3818447c93481c63512f88c279988d258eb4445ed600a0ba9a57a4f29fa8725/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T073603Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=7000f51dfad5d995cfb23bd4c308663f63c95da7d33cb5697daa42429c8dcb12": dial tcp 128.105.82.190:443: i/o timeout
build (hub.opensciencegrid.org/osg-htc/alma10-base:combo, el10, development, 25)
buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: hub.opensciencegrid.org/osg-htc/alma10-base:combo: failed to resolve source metadata for hub.opensciencegrid.org/osg-htc/alma10-base:combo: failed to copy: httpReadSeeker: failed open: failed to do request: Get "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/f3/f3818447c93481c63512f88c279988d258eb4445ed600a0ba9a57a4f29fa8725/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T073606Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=5acb97ca9f6e02b38c3574c7de1f4faca8c9a18442b0909998f3ff47b9cf776b": dial tcp 128.105.82.190:443: i/o timeout
build (hub.opensciencegrid.org/osg-htc/alma10-base:combo, el10, release, 25)
buildx failed with: ERROR: failed to build: failed to solve: hub.opensciencegrid.org/osg-htc/alma10-base:combo: failed to resolve source metadata for hub.opensciencegrid.org/osg-htc/alma10-base:combo: unexpected status from HEAD request to https://hub.opensciencegrid.org/v2/osg-htc/alma10-base/manifests/combo: 500 Internal Server Error
build (docker.io/library/almalinux:9, el9, development, 24)
buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: failed to push hub.opensciencegrid.org/opensciencegrid/software-base:24-el9-development: failed to do request: Head "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/c8/c81ac3563f736b98e789f0a0aa702cc3332908280893e3b1380ba64cc0cb339f/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T075458Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=60cb3d568a95a567e8eef8b830ad7040b6403c2297cb19200d0de4f93c4262d4": dial tcp 128.105.82.190:443: i/o timeout
build (docker.io/library/almalinux:8, el8, development, 24)
buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: failed to push hub.opensciencegrid.org/opensciencegrid/software-base:24-el8-development: failed to do request: Head "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/36/36c4fa9930d51fb012882eadf7958f399421454937c720ad83e54fa65cd2f8cd/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T075552Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=9d14088e42cf48255da55a7d89c5a4fcea6c0e2dd4e238a6a2cba4e4ab789bbb": dial tcp 128.105.82.190:443: i/o timeout
build (docker.io/library/almalinux:9, el9, release, 24)
buildx failed with: ERROR: failed to build: failed to solve: failed to push hub.opensciencegrid.org/opensciencegrid/software-base:24-el9-release: failed to do request: Head "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/77/7724defeffcd7067c3f85bda7c9989aa93942bd065aa7724298fa61a899aedff/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T075825Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=1357e0b2cce06b95967314babd38398ad838c42b80b4cc03fd855e1abaafa71f": dial tcp 128.105.82.190:443: i/o timeout
build (docker.io/library/almalinux:8, el8, testing, 25)
buildx failed with: ERROR: failed to build: failed to solve: failed to push hub.opensciencegrid.org/opensciencegrid/software-base:25-el8-testing: failed to do request: Head "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/41/4169dcdd2cf6dac7538c442716f289d9532bdc3b3b03b69b3d9b0ebcabf34d8d/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T075949Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=bc1d97114bcaee166f66afaf126f1b62c8e2a2789d585fd36870e500af49f227": dial tcp 128.105.82.190:443: i/o timeout
build (docker.io/library/almalinux:8, el8, release, 25)
buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: failed to push hub.opensciencegrid.org/opensciencegrid/software-base:25-el8-release: failed to do request: Head "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/59/597d7deacc9fb93fb585e2c8231df6b598bc2add1efb0b560a5393c0f2bf65d6/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T080123Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=b71f2e6986c5bce9ff701b8ba7495a08ffef84136dd6d08d6c76e1b791961169": dial tcp 128.105.82.190:443: i/o timeout
build (docker.io/library/almalinux:9, el9, testing, 24)
buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: failed to push hub.opensciencegrid.org/opensciencegrid/software-base:24-el9-testing: failed to do request: Head "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/c8/c81ac3563f736b98e789f0a0aa702cc3332908280893e3b1380ba64cc0cb339f/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T080130Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=633d98e36c1f821ec95d62dddcb8f834905fc7cd3cfd892f66ddb97b26c6c6b4": dial tcp 128.105.82.190:443: i/o timeout
build (docker.io/library/almalinux:9, el9, release, 25)
buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: failed to push hub.opensciencegrid.org/opensciencegrid/software-base:25-el9-release: failed to do request: Head "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/4f/4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T080207Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=c6daead2d95803dcc680e2abb69e4fd37f6d29f91b048d5e1c9cf9942050cee5": dial tcp 128.105.82.190:443: i/o timeout
build (docker.io/library/almalinux:9, el9, development, 25)
buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: failed to push hub.opensciencegrid.org/opensciencegrid/software-base:25-el9-development: failed to do request: Head "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/c8/c81ac3563f736b98e789f0a0aa702cc3332908280893e3b1380ba64cc0cb339f/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T080218Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=8872ae96a0afb64ec12b8f3a3878d4a182824536269ff3e233cd58069dff786a": dial tcp 128.105.82.190:443: i/o timeout
build (docker.io/library/almalinux:8, el8, release, 24)
buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: failed to push hub.opensciencegrid.org/opensciencegrid/software-base:24-el8-release: failed to do request: Head "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/36/36c4fa9930d51fb012882eadf7958f399421454937c720ad83e54fa65cd2f8cd/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T080325Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=d3b4f7999ce99008e6660fd8ff20ed829ef5050beb50bf410350168325598565": dial tcp 128.105.82.190:443: i/o timeout
build (docker.io/library/almalinux:8, el8, testing, 24)
buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: failed to push hub.opensciencegrid.org/opensciencegrid/software-base:24-el8-testing: failed to do request: Head "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/41/4169dcdd2cf6dac7538c442716f289d9532bdc3b3b03b69b3d9b0ebcabf34d8d/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T080428Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=ca7c74c994a9897126170816f16ca2e83bac66ea2298e36c1d5a0ffe7fd47d16": dial tcp 128.105.82.190:443: i/o timeout
build (nvidia/cuda:11.8.0-runtime-rockylinux8, cuda_11_8_0, development, 24)
buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: failed to push hub.opensciencegrid.org/opensciencegrid/software-base:24-cuda_11_8_0-development: failed to do request: Head "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/d2/d28605281af974c51e91c5adf06b4e61692f43483e6909dae2f1ad77b19cc489/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T080448Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=618637e7cfb8685f64489d08bdab0e662374140e3d68c9289bda4f0f4697bbe4": dial tcp 128.105.82.190:443: i/o timeout
build (docker.io/library/almalinux:8, el8, development, 25)
buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: failed to push hub.opensciencegrid.org/opensciencegrid/software-base:25-el8-development: failed to do request: Head "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/36/36c4fa9930d51fb012882eadf7958f399421454937c720ad83e54fa65cd2f8cd/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T080727Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=7e3f335db0cd7a700503e1057d73806e72a9b9f3b6085be6395f6c5632425e1e": dial tcp 128.105.82.190:443: i/o timeout
build (docker.io/library/almalinux:9, el9, testing, 25)
buildx failed with: ERROR: failed to build: failed to solve: failed to push hub.opensciencegrid.org/opensciencegrid/software-base:25-el9-testing: failed to do request: Head "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/77/7724defeffcd7067c3f85bda7c9989aa93942bd065aa7724298fa61a899aedff/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T080909Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=74c70ccd3d870958b89d56c86bc43df44bcbfef15949d4addc7eeb370fb15a58": dial tcp 128.105.82.190:443: i/o timeout
build (nvidia/cuda:11.8.0-runtime-rockylinux8, cuda_11_8_0, testing, 25)
buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: failed to push hub.opensciencegrid.org/opensciencegrid/software-base:25-cuda_11_8_0-testing: failed to do request: Head "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/d2/d28605281af974c51e91c5adf06b4e61692f43483e6909dae2f1ad77b19cc489/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T081101Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=f3eb410f39d75777e297aecc850785d6e6f126af2f1c2819d41ede30928aa9a1": dial tcp 128.105.82.190:443: i/o timeout
build (nvidia/cuda:11.8.0-runtime-rockylinux8, cuda_11_8_0, release, 25)
buildx failed with: ERROR: failed to build: failed to solve: failed to push hub.opensciencegrid.org/opensciencegrid/software-base:25-cuda_11_8_0-release: failed to do request: Head "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/d2/d28605281af974c51e91c5adf06b4e61692f43483e6909dae2f1ad77b19cc489/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T081244Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=18a5f9efbd30ed4d4d7479160d9b6cbc641d06ca735678e059710f5d76e982de": dial tcp 128.105.82.190:443: i/o timeout
build (nvidia/cuda:11.8.0-runtime-rockylinux8, cuda_11_8_0, testing, 24)
buildx failed with: ERROR: failed to build: failed to solve: failed to push hub.opensciencegrid.org/opensciencegrid/software-base:24-cuda_11_8_0-testing: failed to do request: Head "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/d2/d28605281af974c51e91c5adf06b4e61692f43483e6909dae2f1ad77b19cc489/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T081301Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=fb9195e1098c671dd25034498b01534c631c7c771bd5ac7fbdd89104c8c21d4d": dial tcp 128.105.82.190:443: i/o timeout
build (nvidia/cuda:11.8.0-runtime-rockylinux8, cuda_11_8_0, development, 25)
buildx failed with: ERROR: failed to build: failed to solve: failed to push hub.opensciencegrid.org/opensciencegrid/software-base:25-cuda_11_8_0-development: failed to do request: Head "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/d2/d28605281af974c51e91c5adf06b4e61692f43483e6909dae2f1ad77b19cc489/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T081417Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=ddde6b8cf5bfb099fdae24ffff8e95a903a7edae2b7ec0b53a4fa9222e73aabf": dial tcp 128.105.82.190:443: i/o timeout
build (nvidia/cuda:11.8.0-runtime-rockylinux8, cuda_11_8_0, release, 24)
buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: failed to push hub.opensciencegrid.org/opensciencegrid/software-base:24-cuda_11_8_0-release: failed to do request: Head "https://s3.harbor.chtc.io/harbor-4bf10ec6-8da1-4f83-a309-82f68ccfbe16/osg-harbor/docker/registry/v2/blobs/sha256/d2/d28605281af974c51e91c5adf06b4e61692f43483e6909dae2f1ad77b19cc489/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GW0INQRDQAU2NNC0EMVJ%2F20260329%2Fus-west-1%2Fs3%2Faws4_request&X-Amz-Date=20260329T081614Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=997cbd56cdcbb287c81c060a0ab05414a96033da1a63d1038132e6ea5dc3d6e6": dial tcp 128.105.82.190:443: i/o timeout
build (hub.opensciencegrid.org/osg-htc/alma10-base:combo, el10, testing, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (hub.opensciencegrid.org/osg-htc/alma10-base:combo, el10, development, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (hub.opensciencegrid.org/osg-htc/alma10-base:combo, el10, release, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (docker.io/library/almalinux:9, el9, development, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (docker.io/library/almalinux:8, el8, development, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (docker.io/library/almalinux:9, el9, release, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (docker.io/library/almalinux:8, el8, testing, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (docker.io/library/almalinux:8, el8, release, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (docker.io/library/almalinux:9, el9, testing, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (docker.io/library/almalinux:9, el9, release, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (docker.io/library/almalinux:9, el9, development, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (docker.io/library/almalinux:8, el8, release, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (docker.io/library/almalinux:8, el8, testing, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (nvidia/cuda:11.8.0-runtime-rockylinux8, cuda_11_8_0, development, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (docker.io/library/almalinux:8, el8, development, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (docker.io/library/almalinux:9, el9, testing, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (nvidia/cuda:11.8.0-runtime-rockylinux8, cuda_11_8_0, testing, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (nvidia/cuda:11.8.0-runtime-rockylinux8, cuda_11_8_0, release, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (nvidia/cuda:11.8.0-runtime-rockylinux8, cuda_11_8_0, testing, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (nvidia/cuda:11.8.0-runtime-rockylinux8, cuda_11_8_0, development, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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 (nvidia/cuda:11.8.0-runtime-rockylinux8, cuda_11_8_0, release, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v4, docker/login-action@v2.2.0, docker/setup-buildx-action@v2.7.0. 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/