Hi,
Just to document that Slicer docker images are now rebuilt every night. This allow to keep working the CircleCI test checking that PR and commits pushed to Slicer code base are not breaking the built.
Scripts driving the build of the docker images, push to dockerhub and update of the repository currently lives on metroplex.kitware Linux build machine. I will publish them when I am back from travelling mid July.
Thanks
Jc
I don’t know if this is expected, but I noticed that “official” slicer docker images take very very long time to start, when used for the purpose of running CLIs:
docker run -ti slicer/slicer-build /usr/src/Slicer-build/Slicer-build/Slicer \
--launch RobustStatisticsSegmenter --help
0.02s user 0.02s system 0% cpu 1:53.94 total
Same CLI run using a docker that downloads and unpacks Slicer binary takes orders of magnitude less time:
docker run -ti fedorov/slicerdockers:4.8.1 /opt/slicer/Slicer \
--launch RobustStatisticsSegmenter --help
0.01s user 0.01s system 1% cpu 1.312 total
Maybe it makes sense to add an “official” Slicer docker image that uses unpacked binary for the users that want to use Slicer functionality from docker, not for building/testing Slicer extensions.
Agreed. That would be a very useful addition.
(Currently, the docker files are hosted on GitHub - Slicer/SlicerDocker: Build, package, test, and run 3D Slicer and Slicer Extensions in Docker. during the project week, we will transfer the repository to the Slicer GitHub organization. )
In the mean time, do not hesitate to fork that repo.
Also worth noting that the scripts used to rebuild and publish the docker images on a daily basis are stored at GitHub - Slicer/SlicerDockerUpdate: Helper scripts allowing to automatically re-build and publish Slicer docker images