-
Notifications
You must be signed in to change notification settings - Fork 14
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
Docker install using install script won't start the bc-server container #29
Comments
Can you run this inside the bluecherry-docker directory:
|
(If you have a license key already installed please deactivate it first) |
Appears to be doing the same thing |
I see the problem, a new build should be pushed in the next few minutes. Try the above commands again shortly. |
well, the rsyslog error is gone, but now it appears to be stuck in a loop and stopping at this: 2023-11-04T01:09:23.064816497Z nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol) Log is attached. |
Did you disable IPv6 on your host for some reason? Are you using Linux as the host? |
Yes, ubuntu 22, and it is disabled. Is there any way to change that with nginx? I really don't want ipv6 enabled on this system as it screws with my openvpn tunnels. |
Okay. You can comment out the server line that has [::]... in /etc/nginx/sites-enabled/default To get into the container run: docker compose exec -it bc-server /bin/bash nano should be installed so once you are in run: nano /etc/nginx/sites-enabled/default If that won't work because docker is respawning I'll come up with another solution when I'm back to a computer |
Yeah, I can't get into it because as soon as I try to spawn a shell it blows up and dies. I'm looking through the dockerfile to see if there's a way I can just remove that line from the default file, or just remove the default file entirely. |
Can you try to pull the latest and see if that works? |
well, after some git repo tomfoolery, I finally got the modified docker-compose.yml and the right build-source repo on my local system, however now it's blowing up with another error and restarting continuously:
just FYI, after changing to the build-source branch in order to check out your changes, the docker-compose.yml in that branch uses the "citesting" docker image, so I changed that back to unstable. |
Ok, so clearing everything out and starting again, by resetting to the master branch and then making manual changes to docker-compose.xml and server/Dockerfile , it appears to be started and running. I will do some further testing to see what happens with it and ensure it stays running. |
Logs are attached. It appears that there's an issue with rsyslog for some reason.
bc-server_logs.txt
The text was updated successfully, but these errors were encountered: