A few months ago I created for a colleague of mine a Galaxy instance using Docker on a virtual machine on our cloud.
After she was done with her analyses and I explained her how to download her results, I deleted the docker container and the virtual machine. I saved the mapping directory “just in case”.
She recently asked me if I could restart the Galaxy instance since she had a problem when saving her datasets.
Now I have troubles starting a new container using the same mapping directory.
I had to go inside the Docker container and manually launch the startup script to get more information.
I had the following error:
Exception: Your database has version ‘134’ but this code expects version ‘141’. Please backup your database and then migrate the database schema by running ‘sh manage_db.sh upgrade’.
So I backuped my database, upgraded postgresql, reimported the backuped database and launched the startup script again.
Now I can access the Galaxy instance but I cannot log to the admin account (which was used by my colleague to do her analyses. She didn’t bother creating a new account). I have no error message but the “admin” tag doesn’t appear and when I click on “user” it says “connected as” with nothing following.
I even tried to import the database backup into a “virgin” Docker container created from the same Galaxy Docker image but there were no datasets in this new instance.
I know the datasets are there. There are a lot of files in mapping/galaxy-central/database/files/000/ but named dataset_XXX.dat. I don’t know where to find the information about the real datasets names, the histories names…
Is there a way to get back the datasets with their metadata?
Thank you for your help.