Corrupted torizon/cross-toolchain-arm64:stable-rc image on DockerHub?

Technical Support
,
1

I am running the command docker pull torizon/cross-toolchain-arm64:stable-rc and this results in an error:

stable-rc: Pulling from torizon/cross-toolchain-arm64
254e724d7786: Already exists 
a9e2d2b7d81d: Pulling fs layer 
ccbaca8ee172: Pulling fs layer 
4f4fb700ef54: Download complete 
5fb07910714b: Waiting 
e9db97cc61d8: Waiting 
04a50263c2b4: Waiting 
20c9e1ff108a: Waiting 
7796a7440d7d: Waiting 
43a623598df6: Waiting 
f0895e78a1a8: Waiting 
7e33f645dfb5: Waiting 
8cffd62f312f: Waiting 
19198f12c063: Waiting 
error pulling image configuration: image config verification failed for digest sha256:3f5cbf39c9a32ccb9f79094220e4464681f6451dadc99bdd221b7ecf361a71df

It seems like the problem is with Torizon dockers only, because I can docker pull debian just fine. How can I proceed?

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer? :+1: :-1:

Hello! Thank you for providing detailed information about your issue.

This error message:

error pulling image configuration: image config verification failed for digest sha256:3f5cbf39c9a32ccb9f79094220e4464681f6451dadc99bdd221b7ecf361a71df

indicates that your Docker client was unable to verify the integrity of the image configuration file during the pull. Since you can pull other images like debian without problems, there could be a few potential causes:

1. Docker Image Cache or Partial/Corrupt Download

Sometimes a previous, incomplete, or corrupted download of the image can cause such errors. Try removing any existing version of the image and re-pulling:

docker image rm torizon/cross-toolchain-arm64:stable-rc
docker pull torizon/cross-toolchain-arm64:stable-rc

2. Network or Proxy Issues

Network instability or disruptions can cause checksum mismatches when downloading large image layers. If you are behind a proxy or in an environment with unreliable network connections, it may help to set up a local Docker registry mirror or proxy. Please refer to the following guide:

3. Docker Version Compatibility

Ensure your Docker Engine is up-to-date. Older versions can sometimes fail to interpret certain manifests. You can check your version with:

docker --version
  • If your version is outdated, consider upgrading Docker.

4. General Docker Health

To ensure your Docker installation is healthy, you can try running a “hello-world” container as a quick test:

docker run --rm hello-world

If this works fine, it confirms your Docker installation is fundamentally working.

5. Retry Later

There might be temporary issues with the Docker Registry or CDN nodes. Sometimes, simply trying again after some time resolves the issue.

Let me know if any of these steps solve your problem, or if you continue experiencing issues!

Best regards,
Toradex AI Assistant.

3

None of the steps solved my problem.

4

Note: I am able to pull torizon/cross-toolchain-arm64:next-rc, so it seems like only some images are corrupted (at the very least stable-rc, 4).

5

Hi @vilchanskyio!

I’ve tested it and it worked as expected.

Could you give more details about your setup and what steps you took before running the command?

Best regards.

6

I was able to pull the image just now, so it seems like the issue was somewhere in the network/transport layer.

7

Hi @vilchanskyio!

I’m glad to know that.

Best regards.