fixed http images #10
Dpbmrelease.yml
on: push
push_database_dockerhub
/
Push Docker image (qdb)
36s
push_jobs_server_dockerhub
/
Push Docker image (qJobsServer)
5m 24s
push_api_dockerhub
/
Push Docker image (qApi)
5m 37s
push_worker_dockerhub
/
Push Docker image (qWorker)
5m 9s
push_database_ghcr
/
Push Docker image (qdb)
48s
push_jobs_server_ghcr
/
Push Docker image (qJobsServer)
4m 45s
push_api_ghcr
/
Push Docker image (qApi)
5m 31s
push_worker_ghcr
/
Push Docker image (qWorker)
5m 6s
push_proxy_http_dockerhub
/
Push Docker image (qproxy)
46s
push_proxy_https_dockerhub
/
Push Docker image (qproxy-https)
28s
push_proxy_http_ghcr
/
Push Docker image (qproxy)
41s
push_proxy_https_ghcr
/
Push Docker image (qproxy-https)
43s
release
3s
push_janitor_dockerhub
/
Push Docker image (qJanitor)
26s
push_janitor_ghcr
/
Push Docker image (qJanitor)
26s
Matrix: test-dockerhub-production-compose-file-http / test-compose-file
Matrix: test-dockerhub-production-compose-file-https / test-compose-file
Matrix: test-ghcr-production-compose-file-http / test-compose-file
Matrix: test-ghcr-production-compose-file-https / test-compose-file
Annotations
2 errors and 29 warnings
|
test-dockerhub-production-compose-file-https / Test compose file on ubuntu-24.04-arm
Final attempt failed. Child_process exited with error code 1
|
|
test-dockerhub-production-compose-file-http / Test compose file on ubuntu-24.04-arm
Final attempt failed. Child_process exited with error code 1
|
|
release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
|
|
push_database_dockerhub / Push Docker image (qdb)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/attest-build-provenance/predicate@1176ef556905f349f669722abf30bce1a6e16e01, actions/attest@ce27ba3b4a9a139d9a20a4a07d69fabb52f1e5bc, actions/checkout@v4, docker/build-push-action@v6, docker/login-action@f4ef78c080cd8ba55a85445d5b36e214a81df20a, docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
push_proxy_http_ghcr / Push Docker image (qproxy)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/attest-build-provenance/predicate@1176ef556905f349f669722abf30bce1a6e16e01, actions/attest@ce27ba3b4a9a139d9a20a4a07d69fabb52f1e5bc, actions/checkout@v4, docker/build-push-action@v6, docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1, docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
push_proxy_https_dockerhub / Push Docker image (qproxy-https)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/attest-build-provenance/predicate@1176ef556905f349f669722abf30bce1a6e16e01, actions/attest@ce27ba3b4a9a139d9a20a4a07d69fabb52f1e5bc, actions/checkout@v4, docker/build-push-action@v6, docker/login-action@f4ef78c080cd8ba55a85445d5b36e214a81df20a, docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
push_proxy_https_ghcr / Push Docker image (qproxy-https)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/attest-build-provenance/predicate@1176ef556905f349f669722abf30bce1a6e16e01, actions/attest@ce27ba3b4a9a139d9a20a4a07d69fabb52f1e5bc, actions/checkout@v4, docker/build-push-action@v6, docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1, docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
push_janitor_ghcr / Push Docker image (qJanitor)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/attest-build-provenance/predicate@1176ef556905f349f669722abf30bce1a6e16e01, actions/attest@ce27ba3b4a9a139d9a20a4a07d69fabb52f1e5bc, actions/checkout@v4, docker/build-push-action@v6, docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1, docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
push_proxy_http_dockerhub / Push Docker image (qproxy)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/attest-build-provenance/predicate@1176ef556905f349f669722abf30bce1a6e16e01, actions/attest@ce27ba3b4a9a139d9a20a4a07d69fabb52f1e5bc, actions/checkout@v4, docker/build-push-action@v6, docker/login-action@f4ef78c080cd8ba55a85445d5b36e214a81df20a, docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
push_janitor_dockerhub / Push Docker image (qJanitor)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/attest-build-provenance/predicate@1176ef556905f349f669722abf30bce1a6e16e01, actions/attest@ce27ba3b4a9a139d9a20a4a07d69fabb52f1e5bc, actions/checkout@v4, docker/build-push-action@v6, docker/login-action@f4ef78c080cd8ba55a85445d5b36e214a81df20a, docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
push_database_ghcr / Push Docker image (qdb)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/attest-build-provenance/predicate@1176ef556905f349f669722abf30bce1a6e16e01, actions/attest@ce27ba3b4a9a139d9a20a4a07d69fabb52f1e5bc, actions/checkout@v4, docker/build-push-action@v6, docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1, docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
push_jobs_server_dockerhub / Push Docker image (qJobsServer)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/attest-build-provenance/predicate@1176ef556905f349f669722abf30bce1a6e16e01, actions/attest@ce27ba3b4a9a139d9a20a4a07d69fabb52f1e5bc, actions/checkout@v4, docker/build-push-action@v6, docker/login-action@f4ef78c080cd8ba55a85445d5b36e214a81df20a, docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
push_jobs_server_ghcr / Push Docker image (qJobsServer)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/attest-build-provenance/predicate@1176ef556905f349f669722abf30bce1a6e16e01, actions/attest@ce27ba3b4a9a139d9a20a4a07d69fabb52f1e5bc, actions/checkout@v4, docker/build-push-action@v6, docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1, docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
push_worker_ghcr / Push Docker image (qWorker)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/attest-build-provenance/predicate@1176ef556905f349f669722abf30bce1a6e16e01, actions/attest@ce27ba3b4a9a139d9a20a4a07d69fabb52f1e5bc, actions/checkout@v4, docker/build-push-action@v6, docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1, docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
push_worker_dockerhub / Push Docker image (qWorker)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/attest-build-provenance/predicate@1176ef556905f349f669722abf30bce1a6e16e01, actions/attest@ce27ba3b4a9a139d9a20a4a07d69fabb52f1e5bc, actions/checkout@v4, docker/build-push-action@v6, docker/login-action@f4ef78c080cd8ba55a85445d5b36e214a81df20a, docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
push_api_dockerhub / Push Docker image (qApi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/attest-build-provenance/predicate@1176ef556905f349f669722abf30bce1a6e16e01, actions/attest@ce27ba3b4a9a139d9a20a4a07d69fabb52f1e5bc, actions/checkout@v4, docker/build-push-action@v6, docker/login-action@f4ef78c080cd8ba55a85445d5b36e214a81df20a, docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
push_api_ghcr / Push Docker image (qApi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/attest-build-provenance/predicate@1176ef556905f349f669722abf30bce1a6e16e01, actions/attest@ce27ba3b4a9a139d9a20a4a07d69fabb52f1e5bc, actions/checkout@v4, docker/build-push-action@v6, docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1, docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
test-dockerhub-production-compose-file-https / Test compose file on ubuntu-24.04
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, nick-fields/retry@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/
|
|
test-dockerhub-production-compose-file-http / Test compose file on ubuntu-24.04
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, nick-fields/retry@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/
|
|
test-ghcr-production-compose-file-https / Test compose file on ubuntu-24.04-arm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, nick-fields/retry@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/
|
|
test-ghcr-production-compose-file-http / Test compose file on ubuntu-24.04-arm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, nick-fields/retry@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/
|
|
test-ghcr-production-compose-file-https / Test compose file on ubuntu-24.04
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, nick-fields/retry@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/
|
|
test-ghcr-production-compose-file-https / Test compose file on ubuntu-24.04
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
test-ghcr-production-compose-file-http / Test compose file on ubuntu-24.04
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, nick-fields/retry@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/
|
|
test-ghcr-production-compose-file-http / Test compose file on ubuntu-24.04
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
test-dockerhub-production-compose-file-https / Test compose file on ubuntu-24.04-arm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, nick-fields/retry@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/
|
|
test-dockerhub-production-compose-file-https / Test compose file on ubuntu-24.04-arm
Attempt 2 failed. Reason: Child_process exited with error code 1
|
|
test-dockerhub-production-compose-file-https / Test compose file on ubuntu-24.04-arm
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
test-dockerhub-production-compose-file-http / Test compose file on ubuntu-24.04-arm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, nick-fields/retry@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/
|
|
test-dockerhub-production-compose-file-http / Test compose file on ubuntu-24.04-arm
Attempt 2 failed. Reason: Child_process exited with error code 1
|
|
test-dockerhub-production-compose-file-http / Test compose file on ubuntu-24.04-arm
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Dpbm~qserver~0IL0PZ.dockerbuild
Expired
|
69.7 KB |
sha256:74071d21d5c1ade3757cf9f7380b22bbbc5320109592bb93ee045a481e01040d
|
|
|
Dpbm~qserver~892D2H.dockerbuild
Expired
|
75.1 KB |
sha256:018c9fcf22b3e395184bfa068c423e3ea6405f2a900dd3ffc0cccf1170b24e53
|
|
|
Dpbm~qserver~A8BNUO.dockerbuild
Expired
|
61.3 KB |
sha256:19acd70f3f3842d70994d9ed9cf305d838239afa229ce96204e1c2711c1ac2ac
|
|
|
Dpbm~qserver~AQGVPV.dockerbuild
Expired
|
79.1 KB |
sha256:e676f54748522e21f310c50885ec15e313e9095b051eca5718fc77cdb6581a13
|
|
|
Dpbm~qserver~DZLPF9.dockerbuild
Expired
|
132 KB |
sha256:e0039f8215251cb8e4c7233abe07de112b9fb643662b6fd2297608ecec27ba13
|
|
|
Dpbm~qserver~ECHBOO.dockerbuild
Expired
|
127 KB |
sha256:605ebca85c27b981f0fe305ec059d5ce949bb38b10141869e2788b0222671a35
|
|
|
Dpbm~qserver~GR3ZQ6.dockerbuild
Expired
|
58.4 KB |
sha256:c0fa4b42a083b9c28bab6906512cdc19d52f5ba18bb03d528e57db48dfc8e2fb
|
|
|
Dpbm~qserver~I1JOOS.dockerbuild
Expired
|
70.7 KB |
sha256:1a5df37a2f05c99cf427e5224d50344c810323d5ba16c425cc7b04ab06230fe4
|
|
|
Dpbm~qserver~J1YI0A.dockerbuild
Expired
|
65.9 KB |
sha256:205c6f15fbd06ffeee81a4edbeddcf34bb8841a7ffeb687c8788527b7f8cead4
|
|
|
Dpbm~qserver~MXGW8G.dockerbuild
Expired
|
67.8 KB |
sha256:d6a1c719d409f1280a1c2b3992cd1950152d95795ec50e54ef78d5bc40d7ee17
|
|
|
Dpbm~qserver~QHOICC.dockerbuild
Expired
|
82.7 KB |
sha256:2f916d9c872793abafb5c572a6a3ef27c66f28b55d96e0a179213149cbb6e604
|
|
|
Dpbm~qserver~QQM3OU.dockerbuild
Expired
|
66 KB |
sha256:58386281d38302223e11a5f1e31092b5bd10124e44d3a1222bf7318d8109f681
|
|
|
Dpbm~qserver~SDOQ6L.dockerbuild
Expired
|
75.6 KB |
sha256:b7c561f14aaa6c17d600f16f7df8e6f672a15a8c4180b0632825a21c8b7797c9
|
|
|
Dpbm~qserver~SE6749.dockerbuild
Expired
|
87.4 KB |
sha256:bc54307d25ba2395ff2e135b1cb7ad4d0bbf3f25f916f834863f8af16d646b8e
|
|