docker-compose up fails with DB error and I can't access web GUI #73
Labels
Comments
|
I am using rancher 1.14.2 on my laptop (not docker directly) as we are not allowed to use docker at our company. Is this issue on netdisco related to: |
|
Hello Im having a similar issue asking for upgrade of db followed the instructions as per README I can actually enter the web gui ,seems to be working . Any clue how to solve this? |
|
I got the same issue. |
|
@thatlostboy : the root cause is @benjofalanga : yours seems to be a different issue, if it persists can you also post the output from the netdisco-postgresql container? @bergernetch : please also post logs, preferably in a new issues since there's already a lot going on here. Sorry nobody got around to look at this for multiple months, Netdisco volunteers are spread quite thin. |
Hey yes here are the logs from the netdisco-postgresql container |
|
I have the same problem: and also to me we interface don't come up. Permission are fine. |
I am unable to provide more logs, got it running somehow but do not remember how..
That is understandable, thanks for checking it at all! |
|
yes that's a bit the trouble here, everything that people post looks somewhat normal. The postgres container has a bit on startup that launches it without listening to network requests, during which potentially a schema upgrade is performed. This leads to some error messages of the other containers, but eventually it should resolve and the web interface starts accepting requests. Here is a full example what a normal first start looks like: While some of that looks worrying, it really isn't. Also maybe not super self-explanatory, the final mean that the web process has successfully started. If you have a large database already, the phase between can take quite long. All that being said, if anybody still doesn't have a running web frontend after a couple minutes, maybe also post a |
|
Just in case you wonder, a huge problem is when running in podman ( RHEL/OL ), where the internal resolution does not work unless the containers run in a single pod . |
Thanks I've put this in a separate issue: #78 - I'll try to give it a spin when I get around to it, I can see how it could not be working with our bind mount instruction, DNS options etc. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
Provide a general summary of the issue in the Title above
when including netdisco config snippets, whitespace matters since it's a yaml file
for github issues it really helps if you include the relevant config parts in a codeblock (code fencing)
see the "code" subject on https://guides.github.com/features/mastering-markdown/ for that)
this should preserve spaces in the issue tracker and make troubleshooting quicker
-->
Expected Behavior
When i run docker-compose up, the containers should come up and i shoudl be able to access the web interface.
Current Behavior
When I run docker-compose up, I get the following error. And I cannot acess the website at https://localhost:5000
Possible Solution
Steps to Reproduce (for bugs)
I following the steps in: https://hub.docker.com/r/netdisco/netdisco
Context
I cannot test netdisco for our environment.
Your Environment
I am not sure how to check the postgresql and backend versions. Here is the relevant output from the docker image ls
Device information
The text was updated successfully, but these errors were encountered: