some more interesting elements:
install_tool_depsinstruction from the dockerfile, and I run it in a container afterwards, it complains about permissions, and suggests to chown -R 1450:1450 /tool_deps/_conda/pkgs/cache
chown -R 1450:1450 /tool_deps/_conda/pkgs/cachethen install_tool_deps starts working fine, and the environments it creates (identical to the non-working ones from before), work fine.
I would say this is a permissions issue. Somehow the mulled environments -which are installed after the startup-lite instruction, are not available to the galaxy user 'admin' for activation.
install_tool_depsneeds a running server in order to work. Ideas?
USER rootwhere you need docker to switch back to acting as root?
install_tool_depsneeds to be run as
galaxyuser in order to create the envs with the correct ownership
install_tool_depsalso needs a running
startup_litein order to work, a galaxy server at localhost:8080 must be alive somehow.
startup_liteneeds to be launched while acting as root, otherwise it gets stuck on 'waiting for database'
install_tool_depswhile a galaxy server is alive
chgrp -R galaxy /tool_deps/_conda/envs && chmod g+s -R /tool_deps/_conda/envsjust after
startup_lite. This way, all the envs that will be placed in that folder will inherit the
galaxygroup ownership. Running
chmod/chuserafter the installation of all the dependencies would have worked as well, but it would be excruciatingly long.