Closed deoliveiralf closed 3 days ago
I'm also getting this error along with the database migration error here: https://github.com/bgruening/docker-galaxy-stable/issues/575
They may be related
Also looks to be the same as: https://github.com/bgruening/docker-galaxy-stable/issues/571
Thanks to @jyotipm29 we are back on track :smile: The new 24.1 image contains a lot of changes and reflects the latest developments in Galaxy. I would like to close this PR, but please feel free to reopen and rebase against the latest version.
Please give it a try:
docker run -p 8080:80 -p 8021:21 -p 4002:4002 --privileged=true -e "GALAXY_DESTINATIONS_DEFAULT=slurm_cluster_docker" -v /tmp/galaxy-data/:/export/ quay.io/bgruening/galaxy:24.1
... or any other combination. The readme has been updated. Please add any useful tip to it.
For a list of changes, see the Changelog.
Hello dears, I novel on bioinformatic jobs. I have tried to install docker-galaxy, however, is there a problem that doesn't work correctly. When I run docker exec gracious_elbakyan supervisorctl status, it returns: lfdeoliveira@Biocel:~$ docker exec gracious_elbakyan supervisorctl status autofs FATAL Exited too quickly (process log may have details) condor RUNNING pid 819, uptime 0:03:27 cron RUNNING pid 698, uptime 0:03:43 docker STOPPED Not started galaxy:galaxy_nodejs_proxy RUNNING pid 749, uptime 0:03:33 galaxy:galaxy_web FATAL Exited too quickly (process log may have details) galaxy:handler0 FATAL Exited too quickly (process log may have details) galaxy:handler1 FATAL Exited too quickly (process log may have details) nginx RUNNING pid 114, uptime 0:04:10 postgresql RUNNING pid 563, uptime 0:04:05 proftpd RUNNING pid 706, uptime 0:03:41 rabbitmq RUNNING pid 115, uptime 0:04:10 reports RUNNING pid 770, uptime 0:03:32
and the localhost:8080 returns 403 Forbidden
any idea what happens? Thanks so much