pi-gen build failed with exit code 1 #9 exporting layers 2.4s done #9 writing image sha256:4df93b184e12de5f56dfd8b7e3f985e91110b1b1527a05f64f33383e740d18c9 done #9 naming to docker.io/library/pi-gen done #9 DONE 2.4s WARNING: current commit information was not captured by the build: git was not found in the system: exec: "git": executable file not found in $PATH real 0m0.352s user 0m0.015s sys 0m0.008s

pi-gen build failed with exit code 1 #9 exporting layers 2.3s done #9 writing image sha256:c1ddda1914f062fa08e7c971271fdd6ef7a8e892e8bb022504189b0ea7538632 done #9 naming to docker.io/library/pi-gen done #9 DONE 2.3s WARNING: current commit information was not captured by the build: git was not found in the system: exec: "git": executable file not found in $PATH real 0m0.367s user 0m0.014s sys 0m0.007s

pi-gen build failed with exit code 1 #9 exporting layers 2.4s done #9 writing image sha256:138c79c5d29939354a7831eb3596f91ef44adf457142c58f173fa43d9f6b4884 done #9 naming to docker.io/library/pi-gen done #9 DONE 2.4s WARNING: current commit information was not captured by the build: git was not found in the system: exec: "git": executable file not found in $PATH real 0m0.661s user 0m0.012s sys 0m0.012s

pi-gen build failed with exit code 1 #9 exporting layers 2.3s done #9 writing image sha256:4ef4bb6d0d9064629802691df1eb4a7b12ac6c68cf50424c904f108f9468ca94 done #9 naming to docker.io/library/pi-gen done #9 DONE 2.3s WARNING: current commit information was not captured by the build: git was not found in the system: exec: "git": executable file not found in $PATH real 0m0.759s user 0m0.010s sys 0m0.011s

pi-gen build failed with exit code 1 #9 exporting layers 2.3s done #9 writing image sha256:4ed07566055083056f7cc62c3cbd71962b585fbdcb8962352ab2166bd0b32ef4 done #9 naming to docker.io/library/pi-gen done #9 DONE 2.4s WARNING: current commit information was not captured by the build: git was not found in the system: exec: "git": executable file not found in $PATH real 0m0.690s user 0m0.011s sys 0m0.012s

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/

WARNING: current commit information was not captured by the build: git was not found in the system: exec: "git": executable file not found in $PATH

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/

WARNING: current commit information was not captured by the build: git was not found in the system: exec: "git": executable file not found in $PATH

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/