@jcfr

Hello Jean-christophe,

Thank you so much for your work. We have been looking at what you did those weeks and it's perfect.

However we still have one issue that we don't know how to solve.
In the dockerfile that you wrote: "L42: ENTRYPOINT bash --init-file /app/slicer-env.sh"
we understood that when the docker will be run, the first script that will be executed will be the slicer-env.sh bash script.

Our problem is that when we tried to run the following command line:
docker run --rm our_docker_name:latest bash /app/a_bash_script.sh --help
nothing happened.

We tried several approaches and the only one that worked is to copy all the paths in the slicer-env.sh into the dockerfile as ENV. But we don't think it's a "clean" solution.

So we have a couple of questions:

• Is there a way to run a bash script even if there is a ENTRYPOINT inside the dockerfile script
• Is there another way to create all the paths for the docker container

If you need more explanation and/or if you have time, we could schedule a meeting if you are available this week.

Thank you very much,
Sincerely,
Romain and Celia

We have created a dockerfile in which we download slicer.

Our aim is to download slicer extensions in a way that is maintainable for other users to easily add other extensions in the future.

To do so, your advice was to install the tar.gz extension in a specific path in the docker container.

Could you please guide us on what you had in mind @jcfr

Thank you