Error starting container - cpu worker
At random times, system logs show the following error and the worker does not start. For the following logs, the worker id is: 1j3jppaqs9jp0k
------
2024-09-11T10:53:06Z worker is ready
2024-09-11T10:53:06Z start container
2024-09-11T10:53:06Z error starting container: Error response from daemon: failed to create task for container: failed to create shim task: Could not create the sandbox resource controller mkdir /sys/fs/cgroup/memory/docker/kata_171b97b3360b8a8be09e406a07d6d9d6669ceb5c147d7b7fca64cb6cd1972e04: no space left on device: unknown
2024-09-11T10:53:23Z start container
2024-09-11T10:53:23Z error starting container: Error response from daemon: failed to create task for container: failed to create shim task: Could not create the sandbox resource controller mkdir /sys/fs/cgroup/memory/docker/kata_171b97b3360b8a8be09e406a07d6d9d6669ceb5c147d7b7fca64cb6cd1972e04: no space left on device: unknown
2024-09-11T10:53:41Z start container
2024-09-11T10:53:41Z error starting container: Error response from daemon: failed to create task for container: failed to create shim task: Could not create the sandbox resource controller mkdir /sys/fs/cgroup/memory/docker/kata_171b97b3360b8a8be09e406a07d6d9d6669ceb5c147d7b7fca64cb6cd1972e04: no space left on device: unknown
2024-09-11T10:53:58Z start container
2024-09-11T10:53:58Z error starting container: Error response from daemon: failed to create task for container: failed to create shim task: Could not create the sandbox resource controller mkdir /sys/fs/cgroup/memory/docker/kata_171b97b3360b8a8be09e406a07d6d9d6669ceb5c147d7b7fca64cb6cd1972e04: no space left on device: unknown
2 Replies
It sounds like you are running out of disk space. How much Container Disk did you allocate for this image? Was it large enough to support your image? The Default value is 5GB which is not big enough for most images.
hey, thanks for reporting this, I notice there are some space issue on the host server, will ping data center engineer to fix it.