Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to pull labring/kubernetes:v1.24.9 image with I/O timeout and outdated Qemu binaries #2041

Open
1 of 2 tasks
jwangkun opened this issue Jan 23, 2025 · 0 comments
Open
1 of 2 tasks

Comments

@jwangkun
Copy link

Search before asking

  • I had searched in the issues and found no similar issues.

Environment

https://laf.dev

What happened

with I/O timeout and outdated Qemu binaries
Body
Problem Description
I'm encountering two issues while trying to set up my environment.
Outdated Qemu Binaries
I'm running an outdated version of Qemu binaries on my host. The architecture of my system is arm64. This might cause potential problems in the virtualization process.
Image Pulling Failure
I'm trying to pull the labring/kubernetes:v1.24.9 image. Here is the detailed command output:

How to reproduce

The error indicates that there is an I/O timeout when trying to connect to the Docker Hub registry.
Environment Information
Operating System: [Please fill in your OS here, e.g., Ubuntu 20.04]
Container Runtime: [Podman or Docker, and its version]
Qemu Version: [The current version of Qemu you are using]
Steps to Reproduce
Set up the environment with the above - mentioned OS and container runtime.
Try to pull the labring/kubernetes:v1.24.9 image using the relevant container runtime command.
Expected Behavior
The Qemu binaries should be up - to - date to ensure smooth virtualization operations.
The labring/kubernetes:v1.24.9 image should be pulled successfully without any I/O timeout errors.
Possible Solutions Tried
Checked the network connectivity by pinging other websites, and the network seems to be working fine.
There are no proxy settings configured in my environment.
I would appreciate any help or suggestions to resolve these issues.

Are you willing to submit PR?

  • Yes I am willing to submit a PR!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant