pi-gen build failed with exit code 1 #9 exporting layers 2.0s done #9 writing image sha256:ebe9a0a4805d980b5497ea042943ee1af666ff633f75a7280c194daef4854e30 done #9 naming to docker.io/library/pi-gen done #9 DONE 2.0s 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.265s user 0m0.009s sys 0m0.011s

pi-gen build failed with exit code 1 #9 exporting layers 2.4s done #9 writing image sha256:f97a4c9f1182c1d2693fe96bf9268b51e347d49b074f074c6369101b3765b171 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.327s user 0m0.008s sys 0m0.014s

pi-gen build failed with exit code 1 #9 exporting layers 2.4s done #9 writing image sha256:ffc452de0e50681eb63478c31f7cf0cd0a33870912665fdb9cbd3f0ac382e3cd 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.687s user 0m0.011s sys 0m0.011s

pi-gen build failed with exit code 1 #9 exporting layers 2.5s done #9 writing image sha256:5eba11200f5bbd7d8c66079939f1719724a4e93a32a51ae39f401d31e32483b3 done #9 naming to docker.io/library/pi-gen done #9 DONE 2.5s 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.679s user 0m0.010s sys 0m0.016s

pi-gen build failed with exit code 1 #9 exporting layers 2.5s done #9 writing image sha256:a6180e85dca1d8afdf143d67846b86de38e56ba3157366071c32df324d2132d9 done #9 naming to docker.io/library/pi-gen done #9 DONE 2.5s 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.353s user 0m0.009s sys 0m0.015s

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/