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

Fix that after a while, docker-desktop has deploys fail, with error "Docker is not responding. Maybe Docker is out of disk space? [...]"; seems to be memory issue #314

Open
Venryx opened this issue May 19, 2024 · 1 comment

Comments

@Venryx
Copy link
Collaborator

Venryx commented May 19, 2024

Likely related to WSL memory limits being reached.

Notes:

  • On my desktop, the WSL memory limit is 8gb.

Possibly related posts/issues

Related to memory:

Highly relevant, to rancher-desktop hang/slowness issue at least):

Cases

  • 2024-05-19 (v-desktop): Docker-desktop showed memory usage of 8.01gb at time of failed deploy. (ie. at WSL memory limit)
  • 2024-05-23 (v-desktop): Issue happened; DD was not showing memory-usage yet, but did show an images list; pressed "Stop" on app-server, to free up a bit of memory; DD then showed memory usage of 8.01gb (ie. at WSL memory limit); Lens was then able to reconnect.

Toward resolution

Notes:

  • Shutting down Docker Desktop, then starting it again, seems to fix the issue temporarily. (that + killing the app-server pod in DD, appears to reduce memory usage by ~450mb)

Next time issue happens, try running in WSL/Ubuntu (in sudo bash): sync; echo 3 > /proc/sys/vm/drop_caches (reduced memory usage by ~2.3gb; unsure if actually helps with the deploy problem though, since it might be "illusory" savings if was just caching memory that would have been auto-dropped as needed anyway)

@Venryx Venryx converted this from a draft issue May 19, 2024
@Venryx
Copy link
Collaborator Author

Venryx commented May 23, 2024

Found a possible fix: (from: microsoft/WSL#8725 (comment))

[wsl]
kernelCommandLine = systemd.unified_cgroup_hierarchy=1 cgroup_no_v1=all

[experimental]
autoMemoryReclaim=gradual

Except I replaced "gradual" with "dropCache" in the above. (note: "dropCache" is the default as of WSL2 v2.2.1)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🔖 Short-term (Venryx)
Development

No branches or pull requests

1 participant