-
Notifications
You must be signed in to change notification settings - Fork 9
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
Exanmple NPM config and compose #59
Comments
We need more information from you here, please set the |
Same configuration here and I'm able to get CN to stop said container, but unable to start it. Did you find amy fix for this? I enabled debug as well and I could clearly see all the steps involved in stopping, but after that nothing else is written in the logs when accessing the domain address. |
That usually means that the traffic isn’t routed through CN in the first place. Thus CN doesn’t know when you want to access the container and can’t start it. |
Figured as much, but I can't find the mistake in the configuration:
Tried using CN both with a bridge between containers and with the local IP as well, but same result.
Am I doing something wrong here? |
Solved by redeploying the container using the host network. |
hello,
i am trying to setup ContainerNursery but i was not able to setup it correctly with NPM can anyone help me ?
My configs are following and only think i get is 502 Bad Gateway.
Can anyone try to point any issues in docker files or in config, since i tryed everything i could, without any sucess
thank you
The text was updated successfully, but these errors were encountered: