Requirements not installed before the start of web server
Closed this issue · 2 comments
For me the galaxy deployment does not check and install needed dependencies before the start of the web server.
Concrete: Configuring auth_conf.xml with <type>ldap3</type> lets Galaxy recognize that python-ldap3 is a dependency. This works when run.sh is triggered. It identifies the dependency and downloads the library.
In the helm chart, the server boots up and does not download this library and hence Active Directory does not work.
Current workaround: Installing the library manually via extraInitCommands
The helm chart deliberately avoids use of the run.sh script, and therefore, conditional dependencies are not automatically installed. This is to, among other things, provide more reproducible builds where transient network failures and the like do not cause the container to fail on startup.
To handle such dependencies, please see this section: https://github.com/galaxyproject/galaxy-docker-k8s/#extending-the-image
See here for how the playbook adds defaults: https://github.com/galaxyproject/galaxy-docker-k8s/blob/e724b3a9dcb6f7be690ce643afc0507bbbad34cc/playbook.yml#L7
Hi nuwang. Thanks for the answer! The playbook defaults look promising. I'll close it here.