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

Image pull jobs failing: "standard_init_linux.go:228: exec user process caused: no such file or directory" #176

Closed
dstndstn opened this issue Jun 3, 2022 · 1 comment
Assignees
Labels
bug Something isn't working
Milestone

Comments

@dstndstn
Copy link

dstndstn commented Jun 3, 2022

Hi,

I'm not sure I'm supposed to be asking a support question here, and I am very new to Kubernetes and kube-fledged, so will appreciate your patience, and apologies if this is foolish...

I'm running a Google Kubernetes Engine cluster, and trying to pre-pull some (~5 GB) images on nodes upon startup, so that subsequent jobs launch quickly.

I am finding that all the image-pull jobs are failing. All I can find in the logs (in the Google Cloud dashboard) for a failed job is

Job imagecache1-272c4:

2022-06-03 11:31:14.910 EDT
standard_init_linux.go:228: exec user process caused: no such file or directory

In the kubefledged-controller logs I see:

I0603 15:31:11.820453       1 image_manager.go:469] Job imagecache1-272c4 created (pull:- docker.io/einsteintoolkit/et-workshop --> gke-cluster-gpu-pool-5f741b22-u479, runtime: containerd://1.5.4)
I0603 15:31:17.928191       1 image_manager.go:217] Job imagecache1-272c4 failed (pull: docker.io/einsteintoolkit/et-workshop --> gke-cluster-gpu-pool-5f741b22-u479)

I'm pretty lost about what's going on, so any pointers would be appreciated. Thanks!

@senthilrch senthilrch self-assigned this Oct 21, 2022
@senthilrch senthilrch added the bug Something isn't working label Oct 21, 2022
@senthilrch senthilrch added this to the v0.10.0 milestone Oct 21, 2022
@senthilrch
Copy link
Owner

This error is caused due to kube-fledged using the busybox image from gcr.io. This image has a dynamically linked echo binary, whereas kube-fledged requires a statically linked one.

This issue will be resolved in v0.10.0 by using the busybox image from dockerhub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants