Closed brianschrameck closed 1 year ago
After MUCH digging, I discovered that I couldn't connect to the container using docker exec -it minecraft-bedrock bash
.
I was getting an error similar to:
OCI runtime exec failed: exec failed: container_linux.go:370:starting container process caused:open /dev/ptmx: no space left on device: unknown
.
I then tried adding the tty
option to my compose file, and got a similar error:
Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: open /dev/ptmx: no space left on device: unknown
Running a ps -ef
on my machine showed that there were dozens of ttyd
daemons seemingly left behind from Docker containers, even after the containers were removed.
killall ttyd
and then restarting this container worked.
This configuration was working correctly for some time. Now I can't make any connections to the server even if I start over and use the default config. The
itzg/minecraft-bedrock-server
container seems to work correctly. Any ideas?