You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to streamline a galaxy flavor for QIIME 2 (q2galaxy), and would like to pre-install the tools with conda. After a bunch of experimentation, I've found the following almost works:
(Note our base image is still derived from docker-galaxy-stable, just compiled on a fork of galaxy with some custom datatypes, hopefully this won't be necessary in the future)
The very last RUN command is able to wait for the galaxy server to spin up, waits a bit longer for the admin user to be created, and then attempts to install everything in the tool config.
(Logs are interleaved here as the startup script is running in the background.)
I imagine what I am doing isn't exactly intended, but after looking through ephemeris and bioblend, I really don't see why this isn't working. When I did not wait for the admin user to be created (with the additional hacky sleep call), I would recieve a 403 immediately, which made sense, and the conda install never started. Here, we can see I clearly passed the @web.require_admin decorator at first... as the conda install proceeds, but then I am getting a 403 after everything appears to have finished.
I have tried using ephemeris with the API key instead, but it is the same situation. Interestingly, at some point the endpoint recieves the API key even if I don't use that in ephemeris (seen above). I can't figure out where in bioblend this even happens, but that might be a clue?
The text was updated successfully, but these errors were encountered:
Hello,
I am trying to streamline a galaxy flavor for QIIME 2 (q2galaxy), and would like to pre-install the tools with conda. After a bunch of experimentation, I've found the following almost works:
(Note our base image is still derived from docker-galaxy-stable, just compiled on a fork of galaxy with some custom datatypes, hopefully this won't be necessary in the future)
The very last
RUN
command is able to wait for the galaxy server to spin up, waits a bit longer for the admin user to be created, and then attempts to install everything in the tool config.This very nearly completes, but ends with a 403:
stdout showing my plight
(Logs are interleaved here as the startup script is running in the background.)
I imagine what I am doing isn't exactly intended, but after looking through ephemeris and bioblend, I really don't see why this isn't working. When I did not wait for the admin user to be created (with the additional hacky
sleep
call), I would recieve a403
immediately, which made sense, and theconda install
never started. Here, we can see I clearly passed the@web.require_admin
decorator at first... as theconda install
proceeds, but then I am getting a403
after everything appears to have finished.I have tried using ephemeris with the API key instead, but it is the same situation. Interestingly, at some point the endpoint recieves the API key even if I don't use that in ephemeris (seen above). I can't figure out where in bioblend this even happens, but that might be a clue?
The text was updated successfully, but these errors were encountered: