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
Thanks for this repo, I haven't been able to figure it out myself for a long time! During usage, I encountered an issue: when I start many new containers and the total memory reaches its limit, containerd crashes and automatically restarts. This causes dockerd to lose connection, and all containers started by the previous containerd process are terminated.
Normally, containerd or dockerd should have higher priority and should kill individual running containers before an out-of-memory (OOM) situation occurs. I don't know how to handle this issue myself.
The text was updated successfully, but these errors were encountered:
Mmm are you sure this isn't a problem of containerd itself? This repository just install docker in a standard ubuntu image. I have no control over it.
Yes, I ve seen the Dockerfile. However in this case, what happens inside the container is indeed different from what happens on the physical machine...
Thanks for this repo, I haven't been able to figure it out myself for a long time! During usage, I encountered an issue: when I start many new containers and the total memory reaches its limit, containerd crashes and automatically restarts. This causes dockerd to lose connection, and all containers started by the previous containerd process are terminated.
Normally, containerd or dockerd should have higher priority and should kill individual running containers before an out-of-memory (OOM) situation occurs. I don't know how to handle this issue myself.
The text was updated successfully, but these errors were encountered: