Closed Tomnl closed 5 years ago
Mh, I never tried this but yes it should work. Do you see the TS in the admin panel from within Galaxy?
Do you need this local TS or can be install the tools in a different way?
Hi @bgruening,
Thanks for the reply.
Yes, I can see the TS in the admin panel from Galaxy when the build is made and running.
If there is another approach to install the tools for the build I would be happy to use that. I just wanted an approach to install tools into the Docker build that are not currently in either the main toolshed or the test toolshed.
What other approaches would you recommend?
Have you seen this here: https://github.com/bgruening/docker-galaxy-stable#Integrating-non-Tool-Shed-tools-into-the-container ?
Thanks! I will give that a try.
Just to check though. I believe these are commands for the "docker run" stage, are there any other options for including non-toolshed tools at the build stage?
Sure everything that you can do during run time can be done during build time. You just need to copy the XML files into the container and provide one of the manually-modified tool_conf.xml files ... thats it.
Thanks Björn. This works well for my purposes. I will close now
FYI: @RJMW
Hi Björn,
I think this issue might be related related to #72
If I wanted to extend the docker image to add a collection of tools, is it possible to install tools from a local toolshed running from the same computer as the docker (or a toolshed running on the same network but not accessible outside the network)?
At the moment when I try to do this I am getting an "Uncaught exception in exposed API method" error.
For example, if I add the following to the Dockerfile:
Where the tool_list.yaml contains:
Where http://172.31.10.181:9009 is running a local toolshed.
I then run the following docker command
docker build -t galaxy-test . --network host
But get the following error when trying to install the tool
FYI: @RJMW