Unexpected EOF

Community Containers
101

I’ve tried the fix but i still have the problem building greenbone from container

102

A post was split to a new topic: Pg-gvm startup loop with Greenbone Community Edition

103

I’ve tried executing the command docker pull registry.community.greenbone.net/community/pg-gvm:stable multiple times, but it always fails with an “unexpected EOF” error (23cded29a8e0). What should I do?

The complete prompt is as follows:
docker pull registry.community.greenbone.net/community/pg-gvm:latest
latest: Pulling from community/pg-gvm
3a0e87375a21: Pull complete
afe9c0915786: Pull complete
e96c9828cda3: Pull complete
585b7e43c0af: Pull complete
23cded29a8e0: Downloading 9.292kB/9.292kB
9497b05c0d7c: Download complete
cff0ccb4617a: Download complete
9fbebbbed3ae: Download complete
7fd0698b9fef: Download complete
f435da0ffbab: Download complete
unexpected EOF

104

The only thing that ospd-openvas is not available on ghcr.io, need to use registry.community.greenbone.net

105

This helped me a lot. Thanks! :smiley:

107

This topic is temporarily closed for at least 4 hours due to a large number of community flags.

108

Hi Greenbone Community Team,

I am reporting a persistent integrity issue with the Docker image community/gvm-config:latest hosted on your official registry (registry.community.greenbone.net).

The image pull fails systematically across multiple independent environments (different hosts, different ISPs, and different networks), while other images like community/gsa:latest are pulled correctly without issues.

Error Details

The download process consistently hangs and fails during the retrieval of a specific small layer (blob), returning the following error:
short read: expected 32 bytes but got 0: unexpected EOF

Technical Evidence

I’ve isolated the issue using skopeo. The tool confirms that the registry declares a 32-byte chunk that it fails to deliver, leading to a termination of the stream:

Getting image source signatures
Copying blob 3a0e87375a21 done
Copying blob 404d07d368b6 done
Copying blob 89984087a32a done
Copying blob 1afdf3f04931 done
Copying blob adbc5d377397 done
Copying blob 58659f65834a done
Copying blob 4f4fb700ef54 [--------------------------------------] 0.0b / 32.0b
FATA[0002] (dest: archive/tar: missed writing 32 bytes): copying system image from manifest list: writing blob: happened during read: unexpected EOF

Troubleshooting Performed

  • Protocol Check: Verified connectivity via openssl s_client -connect registry.community.greenbone.net:443 -tls1_3. Handshake is successful.
  • MTU Testing: Tested with MTU set to 1500, 1450, and 1400 to rule out fragmentation issues.
  • Cross-Environment Test: Replicated the exact same failure on a different machine and a different internet connection.
  • Registry Comparison: docker pull registry.community.greenbone.net/community/gsa:latest works perfectly on the same host.

It appears the gvm-config:latest manifest or one of its underlying blobs is corrupted or missing on your storage backend/CDN.

Could you please verify the integrity of this specific image on the registry and trigger a re-push if necessary?

Best regards.

109

This topic was automatically opened after 24 hours.