search

yandex-cloud / k8s-csi-s3

GeeseFS-based CSI for mounting S3 buckets as PersistentVolumes
Other
571 stars 98 forks source link

transport endpoint is not connected #133

Open 2232729885 opened 3 months ago

2232729885 commented 3 months ago

i install k8s-csi-s3 successfully in hosted k8s, and i mount a minio prefix into pod using static pv successfully.

but one day, the container in pod was killed because linux oom killer, the exist code is 137.

and you know, k8s try restarting the container itself, but the container status continuously waiting, please see below image.

d8f27e9a4a6e7d98e1785f8c5311743

when i delete pod, the restart pod, everything going well. so what's the root cause?

the logs: failed to generate container "16aa862fb1ba30683d5e321bae3ccf177dc55c1ae81a41b824ca2395f0a4b1eb" spec: failed to generate spec: failed to stat "/var/lib/kubelet/pods/2219aa68-92ca-4535-bc87-84a39bb9cb83/volumes/kubernetes.io~csi/jupyterlab-pv-13784056164704/mount": stat /var/lib/kubelet/pods/2219aa68-92ca-4535-bc87-84a39bb9cb83/volumes/kubernetes.io~csi/jupyterlab-pv-13784056164704/mount: transport endpoint is not connected

2232729885 commented 3 months ago

looks like last failed container must be deleted, then the container can restart successfully.