ci: short read: expected xxxxxxxxx bytes but got xxxxxxxxx: unexpected EOF

[fanquake]

This issue is happening semi-frequently. i.e https://github.com/bitcoin/bitcoin/actions/runs/18560885434/job/52909339714?pr=33591#step:9:231:

 #10 [5/5] RUN ["bash", "-c", "cd /ci_container_base/ && set -o errexit && source ./ci/test/00_setup_env.sh && ./ci/test/01_base_install.sh"]
#10 sha256:9ff7145d1456945488a8d8d2466983d85b23a449070f110460965a1547aec2c0 122.68MB / 660.19MB 5.7s
#10 sha256:3d058fa1c6c9853659e7c57f9938cc3e7bc8b256a1221e2fa5dfc955b8055a50 3.86kB / 3.86kB 0.3s done
#10 sha256:948296864369b9bd381893ff3a644420170ca34e65df918140a9304a37d03f30 1.85kB / 1.85kB 0.3s done
#10 sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1 32B / 32B 0.3s done
#10 sha256:4b3ffd8ccb5201a0fc03585952effb4ed2d1ea5e704d2e7330212fb8b16c86a3 29.72MB / 29.72MB 1.7s done
#10 sha256:9ff7145d1456945488a8d8d2466983d85b23a449070f110460965a1547aec2c0 156.24MB / 660.19MB 7.1s
#10 sha256:9ff7145d1456945488a8d8d2466983d85b23a449070f110460965a1547aec2c0 191.89MB / 660.19MB 8.3s
#10 sha256:9ff7145d1456945488a8d8d2466983d85b23a449070f110460965a1547aec2c0 225.44MB / 660.19MB 9.8s
#10 DONE 11.1s

#11 exporting to docker image format
#11 ERROR: short read: expected 660192933 bytes but got 251015612: unexpected EOF
------
 > exporting to docker image format:
------
ERROR: failed to build: failed to solve: short read: expected 660192933 bytes but got 251015612: unexpected EOF
Command '['./ci/test/02_run_container.sh']' returned non-zero exit status 1.

Was mentioned in IRC yesterday as well.

[fanquake]

IRC yesterday: https://github.com/bitcoin/bitcoin/actions/runs/18534138379/job/52824610461

[fanquake]

https://github.com/bitcoin/bitcoin/actions/runs/17769369035/job/50682078335?pr=33117

[maflcko]

Normally, network requests are retried in CI to work around intermittent network issues. I guess it could be tried here as well.

I can take a look next week.

[maflcko]

Similar variation: https://github.com/bitcoin/bitcoin/actions/runs/18713760603/job/53368943173#step:9:165:

Building ci_native_msan image tag to run in
+ docker buildx build --file=/home/admin/actions-runner/_work/bitcoin/bitcoin/ci/test_imagefile --build-arg=CI_IMAGE_NAME_TAG=mirror.gcr.io/ubuntu:24.04 --build-arg=FILE_ENV=./ci/test/00_setup_env_native_msan.sh --build-arg=BASE_ROOT_DIR=/home/admin/actions-runner/_work/_temp --platform=linux --label=bitcoin-ci-test --tag=ci_native_msan --cache-from type=gha,url=http://127.0.0.1:12321/,url_v2=http://127.0.0.1:12321/,scope=ci_native_msan --cache-to type=gha,url=http://127.0.0.1:12321/,url_v2=http://127.0.0.1:12321/,mode=max,ignore-error=true,scope=ci_native_msan --load /home/admin/actions-runner/_work/bitcoin/bitcoin
#0 building with "builder-c409df70-e5b4-4870-bbbc-35cd721af826" instance using docker-container driver

#1 [internal] load build definition from test_imagefile
#1 transferring dockerfile: 842B done
#1 DONE 0.0s

#2 [internal] load metadata for mirror.gcr.io/ubuntu:24.04
#2 ERROR: failed to do request: Head "https://mirror.gcr.io/v2/ubuntu/manifests/24.04": dial tcp [2a00:1450:4010:c1e::52]:443: connect: network is unreachable
------
 > [internal] load metadata for mirror.gcr.io/ubuntu:24.04:
------
test_imagefile:9
--------------------
   7 |     # We never want scratch, but default arg silences a Warning
   8 |     ARG CI_IMAGE_NAME_TAG=scratch
   9 | >>> FROM ${CI_IMAGE_NAME_TAG}
  10 |     
  11 |     ARG FILE_ENV
--------------------
ERROR: failed to build: failed to solve: mirror.gcr.io/ubuntu:24.04: failed to resolve source metadata for mirror.gcr.io/ubuntu:24.04: failed to do request: Head "https://mirror.gcr.io/v2/ubuntu/manifests/24.04": dial tcp [2a00:1450:4010:c1e::52]:443: connect: network is unreachable
Command '['docker', 'buildx', 'build', '--file=/home/admin/actions-runner/_work/bitcoin/bitcoin/ci/test_imagefile', '--build-arg=CI_IMAGE_NAME_TAG=mirror.gcr.io/ubuntu:24.04', '--build-arg=FILE_ENV=./ci/test/00_setup_env_native_msan.sh', '--build-arg=BASE_ROOT_DIR=/home/admin/actions-runner/_work/_temp', '--platform=linux', '--label=bitcoin-ci-test', '--tag=ci_native_msan', '--cache-from', 'type=gha,url=http://127.0.0.1:12321/,url_v2=http://127.0.0.1:12321/,scope=ci_native_msan', '--cache-to', 'type=gha,url=http://127.0.0.1:12321/,url_v2=http://127.0.0.1:12321/,mode=max,ignore-error=true,scope=ci_native_msan', '--load', '/home/admin/actions-runner/_work/bitcoin/bitcoin']' returned non-zero exit status 1.
Error: Process completed with exit code 1.

[maflcko]

I presume the same issue exists for the lint task. Though, the caching there does not seem to work at all. So it could make sense to make the caching work there, and then also add a retry loop there.

Otherwise, there could be Ubuntu APT timeouts like https://github.com/bitcoin/bitcoin/actions/runs/18861389218/job/53820273763?pr=33247#step:4:1053