-
Notifications
You must be signed in to change notification settings - Fork 3
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
Verify support for redhat/centos #88
Comments
The network creation is failing at bin/compose up: |
And here are the errors once I worked around that: ERROR: for mysql.burningflipside.local Cannot start service mysql: driver failed programming external connectivity on endpoint mysql.burningflipside.local (58773e0547ae110cfcd39752744f1f38c0fcf5168ab9b165695b050cec2e8102): ErrCreating mongo.burningflipside.local ... error Creating ldap.burningflipside.local ... done ERROR: for mysql Cannot start service mysql: driver failed programming external connectivity on endpoint mysql.burningflipside.local (58773e0547ae110cfcd39752744f1f38c0fcf5168ab9b165695b050cec2e8102): Error starting userland proxy: listen tcp 0.0.0.0:3306: bind: address already in use ERROR: for mongo Cannot start service mongo: driver failed programming external connectivity on endpoint mongo.burningflipside.local (d86972fb8ff06c5deb0a1a43c5e774fb7e4625e4d3967d8d13b1340a3e50595e): Error starting userland proxy: listen tcp 0.0.0.0:27017: bind: address already in use |
"bind: address already in use" that means you have locally installed and currently running services listening on the same ports docker is trying to use... you should turn off locally installed ldap and mysql processes before launching docker.. |
I need the local mysql and mongo instances. The mongo is for my unifi network controller so I can't work without that. Can I just use my local DBs instead of the docker images? They don't have conflicting DBs in them... |
(x) network conflicts with (y) this suggests to me that you have a lingering network object created in docker which is trying to use the same cidr range .. if this is a network object you created intentionally then spin it down when attempting to use sandbox.. if not intentional destroy it.. |
Yeah I nuked my whole docker network to get around that one.... |
you could configure the sandbox to use your locally installed database and ldap.. and just not start those services (comment them from the docker compose configuration) |
Ok things spin up now, but not able to get anything when I hit the 3100 port. I get 404's... |
Oh and ldap is very, very unhappy in it's container... |
script '/var/www/html/index.php' not found or unable to stat this suggests the source code volume mounts did not happen as expected.. |
The only errors I see are about mongo and mysql (expected) but all my source directories are empty after setup.sh ran. |
your log there shows that setup only attempted to clone the common code repo.. setup calls ./bin/repos to clone repos.. my guess is that you might have an artifact from previous work with this repo.. that file contents dictates which github user or organization from which repos will be cloned i believe this project readme advises you to create forks of all the repos.. |
I have to run the script with sudo to get the docker commands to work on Fedora/Centos. That mucks up the repo check out stuff since my root doesn't have an authorized key for github. Maybe change the checkouts to https just to simplify what can go wrong? |
Ok the ldap container is still crashing as soon as it runs. And I get a 403 trying to access any URL. |
all of my testing and development was performed using OSX and Debian hosts
OSX does not require sudo to run docker commands
Debian can be configured to operate is this fashion as well
all commands and documentation assumes that sudo is not required.
I have been told that redhat/centos systems are different and sudo is required.
I believe this project will still function as intended and should only require prefixing calls to the convenience scripts in the
bin/
directory withsudo
but i am leaving the verification of this to somebody who is more intimately familiar with these distributions.
The text was updated successfully, but these errors were encountered: