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

node disk full #3313

Closed
zffocussss opened this issue Jul 20, 2023 · 9 comments
Closed

node disk full #3313

zffocussss opened this issue Jul 20, 2023 · 9 comments
Assignees
Labels
kind/support Categorizes issue or PR as a support question.

Comments

@zffocussss
Copy link

zffocussss commented Jul 20, 2023

What happened:
node disk is almost full

What you expected to happen:
disk space is available.

How to reproduce it (as minimally and precisely as possible):
everytime I created a cluster,after some hours,it get full

Anything else we need to know?:

Environment:

  • kind version: (use kind version): kind v0.11.1 go1.17.2 darwin/amd64
  • Runtime info: (use docker info or podman info): 20.10.20
  • OS (e.g. from /etc/os-release): Macos Ventura
  • Kubernetes version: (use kubectl version):
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.10", GitCommit:"5c1d2d4295f9b4eb12bfbf6429fdf989f2ca8a02", GitTreeState:"clean", BuildDate:"2023-01-18T19:15:31Z", GoVersion:"go1.19.5", Compiler:"gc", Platform:"darwin/amd64"}
Kustomize Version: v4.5.4
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", BuildDate:"2021-05-21T23:06:30Z", GoVersion:"go1.16.4", Compiler:"gc", Platform:"linux/arm64"}
WARNING: version difference between client (1.24) and server (1.21) exceeds the supported minor version skew of +/-1
  • Any proxies or other special environment settings?:

image

@zffocussss zffocussss added the kind/bug Categorizes issue or PR as related to a bug. label Jul 20, 2023
@zffocussss
Copy link
Author

there are only some docker containers and pvcs.why does the node take up too much disk space?

@stmcginnis
Copy link
Contributor

Runtime info: (use docker info or podman info):

Please actually include the output.

You may have too many things consuming the space in the VM. Try deleting unneeded container images and cleaning things up. If nothing else is needed, you can do a full cleanu with docker system prune -a --volumes.

@liangyuanpeng
Copy link
Contributor

liangyuanpeng commented Jul 20, 2023

Kind and the cluster created by Kind itself will not take up much resources.

You can recreate a kubernetes cluster with kind on a new VM to check it.

@BenTheElder
Copy link
Member

This is #735

@zffocussss
Copy link
Author

I am using MacBook Pro which free disk storage is more than 512G

@stmcginnis
Copy link
Contributor

I am using MacBook Pro which free disk storage is more than 512G

How much space is configured for the Docker Desktop VM though?

@BenTheElder
Copy link
Member

Please see #735
/remove-kind bug
/kind support

It's possible to exhaust disk space for many reasons, and there's limited options for kind to mitigate this.
You'll have to allocated more disk space or recreate the clusters to free up space.

I am using MacBook Pro which free disk storage is more than 512G

Docker on mac runs in a VM which has it's own virtual disk which only goes up to some configured subset of the free space. There's some references to those settings here https://kind.sigs.k8s.io/docs/user/quick-start/#settings-for-docker-desktop

@k8s-ci-robot k8s-ci-robot added kind/support Categorizes issue or PR as a support question. and removed kind/bug Categorizes issue or PR as related to a bug. labels Aug 2, 2023
@stmcginnis
Copy link
Contributor

/close

Cleaning this up. Fairly certain this is a matter of allocating more space for the Docker VM.

@k8s-ci-robot
Copy link
Contributor

@stmcginnis: Closing this issue.

In response to this:

/close

Cleaning this up. Fairly certain this is a matter of allocating more space for the Docker VM.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question.
Projects
None yet
Development

No branches or pull requests

5 participants