Installation failed: "Error: No configured Galaxy instances"

Hi!

I’m trying to install Galaxy following the instructions provided at this link. However, every time the sh run.sh command finishes running, this happens:

...
The Galaxy client build is up to date and will not be rebuilt at this time.
Activating Conda environment: _galaxy_
Activating virtualenv at .venv
Executing: galaxyctl start
Error: No configured Galaxy instances

Galaxy installs all dependencies but fails to start. I also tried testing the container images provided at this link, but every version I tested is showing the same issue when I try to start it:

Apptainer> galaxyctl start
Error: No configured Galaxy instances

I saw in another thread that a possible solution would be to install an older version, but that doesn’t work either.

Does anyone have a solution to this problem or know what might be causing it?

Thanks in advance!

Welcome, @lcs

For this question

You can share more details about your server and OS and we can try to help more.

Then for this question

You had this same trouble with the Docker Galaxy? The updated version? That would be very odd but we can troubleshoot it more. This is the version that is expected to be easier for new administrators to use, and a good choice for scientists who are willing to learn some server administration since so much is pre-configured. Remember that the Docker Galaxy has a dedicated admin guide, so be sure to follow that when first getting things started up – meaning, the instructions are different than the simple get-galaxy guide.

I’ll link these resources so you can review. Maybe try the Docker version again (starting completely over) to see if that is enough, then we can follow up more with your new questions and some clarification about the environment. :slight_smile:

What’s the Singularity image you are using to run Galaxy, and how have you installed Galaxy into that image?

“No configured Galaxy instances” comes from Galaxy’s process manager, Gravity, and means that it can’t find a Galaxy root and config file. If you are executing run.sh from the root of a Galaxy source clone (where there is a lib/galaxy/ directory and config/galaxy.yml(.sample) this should not happen.

2 Likes

Hello! Thank you very much for your help! Indeed, the problem was in the config/galaxy.yml file, which had not been configured correctly.