Report this

What is the reason for this report?

My Kubernetes Show this Error very often during last week

Posted on May 4, 2020

Hi, I don’t know what’s happen almost every deployment , I scale down and Up my Pod will stuck , every namespace show like this, I want to know what kind of this error and how to fix it.

Please advice , Best Regards


MountVolume.SetUp failed for volume “default-token-d48zk” : mount failed: fork/exec /bin/mount: resource temporarily unavailable Mounting command: mount Mounting arguments: -t tmpfs tmpfs /var/lib/kubelet/pods/15633345-6dc6-409c-9fdf-c2d42b2c90fb/volumes/kubernetes.io~secret/default-token-d48zk Output: Failed create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container for pod “mongoexpress-web-6b4697584f-p8dt5”: Error response from daemon: read unix @->@/containerd-shim/moby/8d2f23bdaea45355d6de4660f3bdf8e47409d21f16ebaf3e13f640adce3af82f/shim.sock: read: connection reset by peer: unknown



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Heya,

Just came across this answer and decided to write some general guidelines for anyone who comes across this in the future despite the old question.

The error you’re encountering could be due to exhausted system resources, possibly memory since the message ‘resource temporarily unavailable’ is shown, which relates to kernel limits.

Kubernetes has trouble creating and mounting volumes due to lack of system resources. It’s possible that scaling down/up multiple pods quickly could be responsible for this issue, depending on your Droplet’s resources.

Here are few recommendations for your problem:

  • Check the resource usage on your Droplet. You can do this using the command - free -m for memory and df -h for disk. If your system resources are almost exhausted, consider upgrading your Droplet.
  • Check the logs of your Kubernetes cluster to see if any kubelet errors appear and fix them accordingly.

For a more in-depth analysis on how to handle Kubernetes issues, I’d strongly recommend you to visit this documentation page.

Hope that this helps!

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.