-
Notifications
You must be signed in to change notification settings - Fork 135
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 fails to launch galaxy instance. #1
Comments
For what it's worth, none of the errors seem to matter much. I can get this to work by launching using
Which suggests its some apache related issue. |
@thashim thanks for your bug report. Can you please provide the docker version you are running? It is very strange that you are seeing the Apache welcome page. There should be a redirect to 8080 and you should see a 'not available' page. So I'm not sure why you are seeing this. Ah this reminds me... are you running it under OS-X? |
Docker info gives
Waiting 10 mins does not seem to help and we're running this under ubuntu 14.04 |
If we ssh tunnel port 8080 so that localhost:8080 binds to server:8080, then viewing at localhost:8080 works. However, even setting host = 0.0.0.0 does not allow the docker container to serve content to non-local addresses. From remote, we still get the same apache page. |
I believe my commit (d857363) in the pull request I just made solves this issue. There's a default virtualenv that wants to serve requests on port 80, instead of proxying to the Galaxy server which is on 8080. |
@thashim I meant the docker version. Are you using 1.0 or docker 1.1? I'm just curious why this is not happen to me and my test instances. Matt kindly shared a fix to deactivate the apache standard site. Normally this is not needed but it can't hurt, so please can you test the latest image with Matt's fix included? Galaxy can run on 127.0.0.1 this is usually not a problem and Apache will proxy this and make it available to the outside. |
My bad, we are at
@matted and I share the same set of machines, so his patch is verified to fix my issue. |
@thashim can we close this issue? |
Yes, confimed fixed. |
This pull request will add a few scripts to automatically populate the data library with test data.
Galaxy Docker Compose Setup version 2
migrate from galaxy-central to "galaxy"
using command
docker run -d -p 8080:80 bgruening/galaxy-stable
and accessing port 8080 of the target server gives:Dumping the launch log via docker logs gives
Full log at http://privatepaste.com/9373f62213
Perhaps unrelated, but attempting to build the dockerfile locally gives:
at step
Step 60 : RUN service postgresql start && sleep 5 && python create_galaxy_user.py --user [email protected] --password admin --key admin
The text was updated successfully, but these errors were encountered: