Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mongo Exit Code 1 #21

Closed
Onemanwolf opened this issue Oct 3, 2020 · 5 comments
Closed

Mongo Exit Code 1 #21

Onemanwolf opened this issue Oct 3, 2020 · 5 comments

Comments

@Onemanwolf
Copy link

Starting mongo ...
Starting mongo ... done
Recreating node-codewithdan ... done
nginx is up-to-date
Attaching to redis, mongo, node-codewithdan, nginx
mongo | standard_init_linux.go:211: exec user process caused "no such file or directory"
mongo exited with code 1

Connection error: MongoNetworkError: failed to connect to server [mongo:27017] on first connect [Error: getaddrinfo ENOTFOUND mongo
node-codewithdan | 22:26:39 0|codewithdan | at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26) {
node-codewithdan | 22:26:39 0|codewithdan | name: 'MongoNetworkError',
node-codewithdan | 22:26:39 0|codewithdan | [Symbol(mongoErrorContextSymbol)]: {}
node-codewithdan | 22:26:39 0|codewithdan | }]

@DanWahlin
Copy link
Owner

Guessing you're on Windows?

I just ran it on Mac and things work properly but something definitely changed for Mongo when running this on Windows as I'm seeing the same error. I'll dig into it when I get some free time. I suspect it's volume or directory security related but hard to say.

@DanWahlin
Copy link
Owner

DanWahlin commented Oct 4, 2020

I'm running WSL (WSL2 actually) on Windows 10 with Docker and it turns out you have to clone the repo using a WSL (Linux) command prompt rather than a Windows command prompt. From there Node has to be installed into WSL if it's not already and then you can run through the instructions in the readme. Worked great once I cloned it using the Linux shell.

Readme has been updated to mention these changes. I'm hoping that's the issue you're hitting as well.

@Onemanwolf
Copy link
Author

Onemanwolf commented Oct 4, 2020 via email

@DanWahlin
Copy link
Owner

DanWahlin commented Oct 5, 2020

Happy to help - thanks. I didn't want to close this out until I knew you had it working (it sounds like you have it working but I wanted to double-check). Thanks for letting me know about the issue.

@DanWahlin
Copy link
Owner

Going to close this out since I'm guessing you're all set. Feel free to re-open if there's still a problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants