Sometimes, pygmy status can report that it's all running with no successful connections.
We should change the prompt to restart pygmy/docker to only be applicable under these conditions.
This would allow pygmy to correctly be able to identify a system error, opposed to a configuration error.
Presently the steps to resolve this are to restart pygmy, or if the problem persists to completely restart docker - and unfortunately I've only seen this problem occur on MacOS...
Sometimes,
pygmy statuscan report that it's all running with no successful connections.We should change the prompt to restart pygmy/docker to only be applicable under these conditions.
This would allow pygmy to correctly be able to identify a system error, opposed to a configuration error.
Presently the steps to resolve this are to restart pygmy, or if the problem persists to completely restart docker - and unfortunately I've only seen this problem occur on MacOS...