Spinalcordtoolbox new docker build chain

[AlexVCaron]

Hello !

I'm currently developing a new Docker build procedure for the spinalcordtoolbox. I was able, using a multi-stage build, to reduce the size of the produced image significantly (~7Gb). From now on, there'll also be docker inage releases following each code release of the toolbox.

I think it'd be of interest to update the build procedure of the container you distribute for NeuroDesktop to benefit from those advantages.

Do you think doing such is possible ? I saw going through documentation you are using NeuroDocker quite extensively, is there a way to reuse an existing docker image or recipe ? I'd be more than willing to contribute such upgrade.

Thank you for your time !

[Vbitz]

Yes you can have containers use existing images if you publish them. For example that's how we distribute fmriprep https://github.com/neurodesk/neurocontainers/blob/main/recipes/fmriprep/build.yaml

We recently wrote our own dockerfile generator compatible with Neurodocker but architected differently internally with the goal of eventually supporting multi-stage builds. We're not quite there yet though.

[AlexVCaron]

That's great, I'll take example on this build to update the current build recipe for spinalcordtoolbox on the neurocontainer repository.

The PR with the new build on our end is here, if interested. We'll have to wait for next release to have an artifact to link, but I'll propose the necessary changes soon so it's ready.

[Vbitz]

Looks great. Looking forward to the PR.

You might also find our testsuite useful https://github.com/neurodesk/neurocontainers/blob/main/recipes/spinalcordtoolbox/fulltest.yaml

It's built for our runner in the repo but I'll investigate how to make it more accessible.

[stebo85]

That's great to hear @AlexVCaron - as soon as you publish the image we will use it as our base-container - that will save us buildtime and maintenance work :)