Process returned exit code 1 Launched as "/home/runner/actions-runner/cached/2.334.0/externals/node20/bin/node /home/runner/work/_actions/Wandalen/wretry.action/v3.8.0_js_action/src/Runner.mjs /home/runner/work/_actions/Wandalen/build-push-action/dist/index.js" Launched at "/home/runner/work/wordpress-ci-container/wordpress-ci-container" Attempts exhausted, made 3 attempts : Attempt #1 started at : 15:24:07 GMT+0000 (Coordinated Universal Time) Attempt #2 started at : 15:27:34 GMT+0000 (Coordinated Universal Time) Attempt #3 started at : 15:30:58 GMT+0000 (Coordinated Universal Time)

buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip -V && PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip install --upgrade pip && PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip install -r /tmp/requirements.txt" did not complete successfully: exit code: 1

buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip -V && PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip install --upgrade pip && PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip install -r /tmp/requirements.txt" did not complete successfully: exit code: 1

buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip -V && PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip install --upgrade pip && PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip install -r /tmp/requirements.txt" did not complete successfully: exit code: 1

The strategy configuration was canceled because "build_push_to_dockerhub.php_8_1-bullseye" failed

The operation was canceled.

buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip -V && PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip install --upgrade pip && PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip install -r /tmp/requirements.txt" did not complete successfully: exit code: 1

buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip -V && PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip install --upgrade pip && PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip install -r /tmp/requirements.txt" did not complete successfully: exit code: 1

The strategy configuration was canceled because "build_push_to_dockerhub.php_8_1-bullseye" failed

The operation was canceled.

buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip -V && PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip install --upgrade pip && PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip install -r /tmp/requirements.txt" did not complete successfully: exit code: 1

buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip -V && PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip install --upgrade pip && PIP_BREAK_SYSTEM_PACKAGES=1 python3 -m pip install -r /tmp/requirements.txt" did not complete successfully: exit code: 1

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3, Wandalen/wretry.action@v3.8.0_js_action. 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/

ERROR: no builder "builder-c2ead150-193e-4711-bf60-8eb50d40e2af" found

InvalidDefaultArgInFrom: Default value for ARG $PHP_IMG results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3, Wandalen/wretry.action@v3.8.0_js_action. 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/

ERROR: no builder "builder-4c18654a-365f-4900-85e7-4ef830562865" found

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

InvalidDefaultArgInFrom: Default value for ARG $PHP_IMG results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3, Wandalen/wretry.action@v3.8.0_js_action. 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/

ERROR: no builder "builder-d1f29dd9-3a8e-4292-b330-73257b65b7e1" found

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

InvalidDefaultArgInFrom: Default value for ARG $PHP_IMG results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3, Wandalen/wretry.action@v3.8.0_js_action. 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/

ERROR: no builder "builder-ceeea856-1414-4b8d-a190-393a766e0598" found

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3, Wandalen/wretry.action@v3.8.0_js_action. 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/

ERROR: no builder "builder-32737c7e-3c3e-4da8-92e8-d1261ee29936" found

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3, Wandalen/wretry.action@v3.8.0_js_action. 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/