This just started happening today out of nowhere. I had a Galaxy Docker instance running fine for several days, but had to take it down. When I tried to start a new instance, Galaxy will not load. Docker reports no errors, but when I try to navigate to the Galaxy instance's URL, nothing loads and it says "Can't connect to server". I've tried several times, and this happens every time now. This is the command I am using to start a new Galaxy Docker instance:
docker run --name galaxy_test --cidfile=$PID_file -d -p 8080:80 -p 8021:21 -v $GALAXY_STORAGE_DIR:/export/ bgruening/galaxy-deeptools
I need to have a "production" and a "test" instance, so I gave it a name with the
--name galaxy_test flag. I ran into this problem with duplicate names so I ran
docker rm <name> on all the old container instances. Now, none of the new ones I make work. If I enter the container and run
nginx, the browser page changes to a 403 Error, but thats it. Is there any documentation on how to actually run Galaxy from within the container? I am not sure what other programs within the container I need to look at for troubleshooting.
EDIT: As a followup, after waiting 20+ minutes, Galaxy is finally starting in these instances. Any ideas why it is taking so long when there was never a delay before?