could not start sbot after crash

[marylychee]

root@ssb-pub:~# docker start sbot
Error response from daemon: OCI runtime create failed: container with id exists: 823319aecc21969612bd995cc2cf32ebfcaa3919c4a944abf7c893b52aa8df6c: unknown
Error: failed to start containers: sbot

[ahdinosaur]

@marylychee and i debugged her pub in-person, turns out the cron.hourly script was failing to run docker start sbot because of the above error. i'm not sure why or how this happens, but the workaround is to docker rm sbot and ./create-sbot.

[johanbove]

I am experiencing the same "error response from daemon" error. Could it be that we're missing a swap memory configuration in the docker container?

I also get this error when starting performing the actions in @ahdinosaur 's reply:

 Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.

I am not sure how to resolve the cgroup is not mounted issue.