The title says it all. I want a docker image of slicer with elastix extension preinstalled. My current Dockerfile is the following: # start from base with centos & qt5 FROM slicer/buildenv-qt5-centos7:latest WORKDIR /usr/src # get basics for the gui RUN yum install Xvfb Xorg mesa-dri-drivers libG…

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…

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 = slicer.app.extensionsManagerModel()…

[image] Sam_Horvath: slicer/buildenv Also 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…

Sorry slicer/buildenv should have been slicer/buildenv-qt5-centos7:latest slicer/slicer-base does not contain a slicer build, it is used for CircleCI builds and so contains everything except Slicer We currently do not have a supported full Slicer docker image. There is a very out of date on…

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 https://github.com/ihnorton/dockerfiles/blob/master/slicer2binder/Dockerfile Once we have such a base image, …

[image] jcfr: It could be based of the work of @ihnorton . See 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 #####…

[image] jcfr: The Dockerfile that would be responsible to create a docker image useful for runtime could simply download the nightly build and extract it. I have tried this approach and in the test it will fail with CMake Error at CMakeLists.txt:17 (find_package): By not providing "FindSli…

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

Build Slicer docker image with preinstalled elastix

Support

lassoan (Andras Lasso) December 30, 2021, 5:59pm 22

The question is answered here:

Topic		Replies	Views
Required extension not being installed in tests Support extensions-manager	20	1029	March 5, 2020
Test extension in Docker Support extensions-manager , docker , testing	14	1034	August 30, 2019
Workflow with Docker and Slicer Support	9	2697	February 3, 2023
Docker container with 3D Slicer build to build and test an extension SlicerDMRI docker , extensions	0	490	October 29, 2023
Installing extension inside a Dockerfile Support	17	1432	January 1, 2022

Build Slicer docker image with preinstalled elastix

Related topics