You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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
In the kubefledged-controller logs I see:
I'm pretty lost about what's going on, so any pointers would be appreciated. Thanks!
The text was updated successfully, but these errors were encountered: