Problem adding/checking a docker tool



I continue the thread I started
I did look at the huge configuration file pointed by @bjoern.gruening at

For testing, I set up a simple busybox image and a tool. The code of the tool is below. To make the tool be executed in the docker container, I must define the default destination of jobs to “docker_local” in the file job_conf.xml. When letting the default to “local”, the tool is executed in the Galaxy shell not on the busybox one. Could somebody tell me what’s wrong, ie galaxy is not selecting the right runner on its own in my configuration?

“config/job_conf.xml” begins with

<?xml version="1.0"?>
<!-- A sample job config that explicitly configures job running the way
     it is configured by default (if there is no explicit config). -->
        <plugin id="local" type="runner" load="" workers="4"/>
    <destinations default="local">
        <!-- Destinations define details about remote resources and how jobs
             should be executed on those remote resources. -->
        <destination id="local" runner="local"/>
        <destination id="docker_local" runner="local">
          <param id="docker_enabled">true</param>


<tool id="dockr_test" name="dockr test" version="0.1.0">
    <container type="docker">busybox</container>
  <description>dcker test</description>
echo "Hello!!!";
uname -a;
df -h > ${output};
if [ -d ${input} ]; then ls -l ${input}; fi;
    <param name="input" type="text" label="Directory" value="">
    <data name="output" format="txt" />

This tool checks the docker execution.

head config/tool_conf.xml

<?xml version='1.0' encoding='utf-8'?>
<toolbox monitor="true">
  <section id="test" name="Testing">
    <tool file="docker/dockrtest.xml" />

docker images

REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
...others not shown here...
busybox             latest              59788edf1f3e        2 months ago        1.15MB
hello-world         latest              4ab4c602aa5e        2 months ago        1.84kB


I read again the documentation mulled_containers.rst. I used the catDocker.xml tool (also at old repo with explanations) to do some more tests.

  • When the default destination is set to local, whatever the container value is, the script is executed without error.
  • When the default destination is set docker_local, if the container is not already installed, an error is raised.

Therefore I have the feeling that the resolver is not detecting the dependency to a specific docker image.I would appreciate some feedback.