Is it possible to not hardcode HOME in Dockerfile?

[yarikoptic]

ATM https://github.com/nipreps/mriqc/blob/master/Dockerfile#L164

ENV HOME="/home/mriqc"

which then gets inherited also within singularity container we convert docker container into in https://github.com/ReproNim/containers so it is "hardcoded" even if I would run in singularity with current user, and thus having no /home/mriqc. As a result we get

>      File "/opt/conda/lib/python3.11/pathlib.py", line 1116, in mkdir
>        os.mkdir(self, mode)
>    OSError: [Errno 30] Read-only file system: '/home/mriqc/.cache'

[oesteban]

Is it not possible to bind some writeable filesystem into /home/mriqc?

[yarikoptic]

it is possible as a workaround and that is what I recommended in poldracklab/tacc-openneuro#86 (comment) and I believe tried/used. But that is not a generic "solution" for https://github.com/ReproNim/containers since it requires this app+version specific knowledge of needing such a workaround.

[asmacdo]

I was able to work around this problem by adding --no-datalad-get to the mriqc args. That does require running datalad get outside of the container.

So I think the problem is that if the MRIQC Dockerfile sets HOME, that will break datalad integration when the container is run with apptainer.