Build Slicer docker image with preinstalled elastix

Somehow I see the slicer-base image to be empty, is this normal? Where it is Slicer installed here?

E15TY:~ alexvergaragil$ docker run -it slicer/slicer-base  /bin/bash
[root@01a14648b5d2 Slicer-build]# ls /usr/src/
cmake-3.13.4-Centos5-x86_64  debug  kernels  Slicer-build
[root@01a14648b5d2 Slicer-build]# ls Slicer-
Slicer-build/  Slicer-prefix/
[root@01a14648b5d2 Slicer-build]# ls Slicer-build/
[root@01a14648b5d2 Slicer-build]# ls Slicer-prefix/
src  tmp
[root@01a14648b5d2 Slicer-build]# ls Slicer-prefix/src/
[root@01a14648b5d2 Slicer-build]# ls Slicer-prefix/src/Slicer-stamp/
[root@01a14648b5d2 Slicer-build]# ls Slicer-build/share/
[root@01a14648b5d2 Slicer-build]# ls Slicer-build/share/Slicer-4.11/
[root@01a14648b5d2 Slicer-build]#

for the version from slicer/buildenv:

Building the Extensions Index does not install the extensions. You will still need to manually install by setting module paths

Can you post the error where slicer fails to start?

Please remember this is a docker container, I can’t start slicer there. Also the slicer-base image is supposed to have a prebuilt image of Slicer, I just need to add the elastix extension by default. I can trigger the instalation in Slicer by:

import slicer
emm =
md = emm.retrieveExtensionMetadataByName('SlicerElastix')

but in the docker environment this fails with the error:

Traceback (most recent call last):
  File "", line 2, in <module>
    emm =
AttributeError: module 'slicer' has no attribute 'app'
vtkDebugLeaks has found no leaks.


E15TY:~ alexvergaragil$ docker run -it slicer/buildenv  /bin/bash
Unable to find image 'slicer/buildenv:latest' locally
docker: Error response from daemon: pull access denied for slicer/buildenv, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'.
  1. Sorry slicer/buildenv should have been slicer/buildenv-qt5-centos7:latest

  2. slicer/slicer-base does not contain a slicer build, it is used for CircleCI builds and so contains everything except Slicer

  3. We currently do not have a supported full Slicer docker image. There is a very out of date one available under slicer/slicer-build

I am looking into the best way to get this working for you (@jcfr )

The Dockerfile that would be responsible to create a docker image useful for runtime could simply download the nightly build and extract it.

It could be based of the work of @ihnorton. See

Once we have such a base image, anyone could easily create derived image with whatever extension they would like.


Thanks for pointing this to me, however I still got some problems:

My Dockerfile so far:

# start from base with slicer-base
FROM slicer/slicer-base

RUN mkdir /usr/src/Slicer && cd /usr/src/Slicer

WORKDIR /usr/src/Slicer

# Download and unpack Slicer
RUN pip install pip beautifulsoup4 2to3 -U
RUN git clone && \
    mv f49c5062695562370a76222dada47e47/ ./
RUN python3 /usr/src/Slicer

# Create evioronment variables
ENV PATH="${PATH}:/usr/src/Slicer/bin"
ENV PYTHONPATH="${PYTHONPATH}:/usr/src/Slicer/bin/PythonSlicer"
ENV SLICER=/usr/src/Slicer

# Install Elastix
RUN PythonSlicer -c "import sys;print(sys.path)"  && \
    PythonSlicer -m pip install --upgrade pip lmfit
RUN 2to3 -w /usr/src/Slicer/lib/Python/lib/python3.6/site-packages/uncertainties
RUN (echo "import slicer"; echo "emm ="; echo "md = emm.retrieveExtensionMetadataByName('SlicerElastix')"; echo "emm.down$
RUN PythonSlicer

# start running container
CMD bash

this is failing at:

Step 12/14 : RUN (echo "import slicer"; echo "emm ="; echo "md = emm.retrieveExtensionMetadataByName('SlicerElastix')"; echo "emm.downloadAndInstallExtension(md['extension_id'])" ) >>
 ---> Running in 5d79f9d8ac46
Removing intermediate container 5d79f9d8ac46
 ---> cbd1129c5580
Step 13/14 : RUN PythonSlicer
 ---> Running in 10b10c6e2546
No module named 'logic'
Traceback (most recent call last):
  File "", line 2, in <module>
    emm =
AttributeError: module 'slicer' has no attribute 'app'
vtkDebugLeaks has found no leaks.
The command '/bin/sh -c PythonSlicer' returned a non-zero code: 1

What is it wrong here? The failing script is this one:

RUN (echo "import slicer"; \
     echo "emm ="; \
     echo "md = emm.retrieveExtensionMetadataByName('SlicerElastix')"; \
     echo "emm.downloadAndInstallExtension(md['extension_id'])" ) >>

I have tried this approach and in the test it will fail with

CMake Error at CMakeLists.txt:17 (find_package):
  By not providing "FindSlicer.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "Slicer", but
  CMake did not find one.

  Could not find a package configuration file provided by "Slicer" with any
  of the following names:


  Add the installation prefix of "Slicer" to CMAKE_PREFIX_PATH or set
  "Slicer_DIR" to a directory containing one of the above files.  If "Slicer"
  provides a separate development package or SDK, be sure it has been

The CMakeList.txt in my extension is:

cmake_minimum_required(VERSION 3.5)


# Extension meta-information
set(EXTENSION_CONTRIBUTORS "Alex Vergara Gil (INSERM) and Janick Rueegger (KSA)")
set(EXTENSION_DESCRIPTION "This extension contains the entire dosimetry workflow for a multipoint study")
set(EXTENSION_DEPENDS SlicerElastix) # Specified as a space separated string, a list or 'NA' if any

# Extension dependencies
find_package(Slicer REQUIRED)

# Extension modules


option(ENABLE_TESTS "Enable tests" OFF)

but my extension is just a python module, Is there a way to avoid the find_package(Slicer REQUIRED) line??

You need to pass -DSlicer_DIR:PATH=... to CMake when you configure Dosimetry4D (or the extension manager index builder project).

I have done that, but that path does not contain any cmake file in the nightly build. You can use docker run -it unnmdnwb3/slicer3d-nightly:0.8.0 /bin/bash to test this approach. It contains a slicer-base image with a preinstalled slicer-nightly. the Slicer_DIR is /usr/src/Slicer

I see. An install tree is not sufficient for build&test. As a workaround, you could create a script that runs Pytjon selftests manually. You can find the full command-line of each test on CDash.

Actually I only require the slicerMacroBuildScriptedModule macro definition to run the tests. This file does not depend on any slicer header, but is the one who builds the python module.
Are the command lines like this one?

/usr/src/Slicer-build/Slicer-build/Slicer "--no-splash" "--testing" "--no-main-window" "--additional-module-paths" "/builds/dosimetry4d-build/lib/Slicer-4.11/qt-scripted-modules" "/builds/dosimetry4d-build/lib/Slicer-4.11/cli-modules" "/builds/dosimetry4d-build/lib/Slicer-4.11/qt-loadable-modules" "--python-code" "import slicer.testing; slicer.testing.runUnitTest(['/builds/dosimetry4d-build/Dosimetry4D/Logic', '/builds/opendose/opendose4d/Dosimetry4D/Logic'], 'Dosimetry4DTest')"


It would be nice to properly build and test your extension. It would increase the test coverage (it would test building) and you never know when you’ll need to add a loadable or CLI module to your extension.

I can perform normal test without elastix, but that will truncate half the functionality of my extension. Is it possible to have a build sequence that leaves me with a built Slicer+Elastix by default?

Are you still trying to do the following:

want a docker image of slicer with elastix extension preinstalled

If yes, there is no need to base your image of slicer/slicer-base. Using a centos7 base should be sufficient.

Also, what would you like to do with this docker image ?

I want to test my extension wich depends on elastix

I have tried to run manually the tests and this happens

$ /usr/src/Slicer/bin/PythonSlicer -c "import slicer.testing; slicer.testing.runUnitTest(['$CI_BUILDS_DIR/dosimetry4d-build/Dosimetry4D/Logic', '$CI_BUILDS_DIR/opendose/opendose4d/Dosimetry4D/Logic'], 'Dosimetry4DTest')"
Dosimetry4DTest (unittest.loader._FailedTest) ... ERROR

ERROR: Dosimetry4DTest (unittest.loader._FailedTest)
ImportError: Failed to import test module: Dosimetry4DTest
Traceback (most recent call last):
  File "/usr/src/Slicer/lib/Python/lib/python3.6/unittest/", line 153, in loadTestsFromName
    module = __import__(module_name)
  File "/builds/dosimetry4d-build/Dosimetry4D/Logic/", line 3, in <module>
    from slicer.ScriptedLoadableModule import ScriptedLoadableModuleTest
  File "/usr/src/Slicer/bin/Python/slicer/", line 4, in <module>
    import qt, ctk, slicer
  File "/usr/src/Slicer/bin/Python/qt/", line 19, in <module>
    from PythonQt.private import QObject
ModuleNotFoundError: No module named 'PythonQt'

Ran 1 test in 0.000s

FAILED (errors=1)
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/src/Slicer/bin/Python/slicer/", line 26, in runUnitTest
  File "/usr/src/Slicer/bin/Python/slicer/", line 11, in exitFailure
    raise Exception(message)
No module named 'logic'
path: ['/builds/dosimetry4d-build/Dosimetry4D/Logic', '/builds/opendose/opendose4d/Dosimetry4D/Logic']
testname: Dosimetry4DTest
vtkDebugLeaks has found no leaks.

I think preinstalled slicer leads to even more errors than building it

I have succeeded to make a Full Test using BrainsFit, not optimal but good enough solution. The Full Test in graphical mode (Reload and test) will use elastix if it is installed.
The module is complete, I am just waiting for testers answers. Next steps will be:

  1. Write the article (shall be presented in ECMP2020 or EANM2020)
  2. Open the source (as soon as the abstract is accepted)
  3. integrating in Slicer as scripted module (I will need your help in this point). The module shall be accesible by the time the article is published.
1 Like

could you tell me how to install extension(such as SlicerRT) in docker container(from docker images manually?

The question is answered here: