Open alaric-dotmesh opened 6 years ago
Killing the running containers (docker rm -f dotscience-app-aa5c8742 dotscience-webhookrelay-aa5c8742 dotscience-committer-aa5c8742 ds-aa5c8742-26ca-4fdc-a0fd-278e588ed82d
) then re-trying to start jupyter fixed it.
On further investigation, this seems to happen when #595 also happens - suggesting that the underlying problem is the dotmesh server container is unavailable when dm
tries to look it up in DNS to connect to it.
That may be the underlying problem, but dm
crashing when a DNS lookup fails is still a bug.
When running the clone command as part of firing up Jupyter, I got a lovely message that seems to be a SIGSEGV from inside the
dm
client:It retried several times, the same effect each time.