Closed youpko closed 2 years ago
This doesn't really make sense, CoreDNS has no impact on the rest of your application. You should be able to leave it out and it runs fine. I would check the netmaker logs with "docker logs netmaker" and make sure it runs successfully. Also, you need to specify in netmaker environment variables 'DNS_MODE=off' so that the server does not attempt to use dns.
I have spent most of yesterday trying to figure out what goes wrong. still no luck.
I have noticed that the reference stack creates 3 volumes but it only specifies 2.
I deployed the stack with Portainer, but I have never seen a generated volume like this.
In the logs (viewed from Portainer) didn't show any errors or other usefull information. is there some logging level I need to set to see more info in the output logs?
Set VERBOSITY = 2 (or 3) in the environment settings of netmaker. That will increase the log level. Also, please paste your compose file here (you can hide sensitive info) since that will help explain what's happening.
I am not aware of an extra volume with a long hash name...not sure where you're getting that from.
@youpko closing as there has not been an update
Using the reference docker compose stack I ran in to a problem.
I disabled the coredns in the compose stack.
Steps:
And now everything works fine until I restart the stack.
Restarting the stack works fine but the web UI prompts to create a new admin user which already exists. This will of course fail and there is no option to log in.