Using docker I replicate this error if I change the container name. When you redeploy it is not resolving mongo0 to itself like it did when you did the re.initiate
Hope this can help in your troubleshooting.
Using docker I replicate this error if I change the container name. When you redeploy it is not resolving mongo0 to itself like it did when you did the re.initiate
Hope this can help in your troubleshooting.