Niklas Schandry

The tests fail because the local container is not called e.g. `busybox` or `ubuntu` but `container_busybox` or `container_ubuntu`. This could be changed, I was mainly worried about problems arising from...

I do not really know why the tests for the Cache fail. The only changes I made were adding the registry, and changing where the lockfile is placed, but I...

I think I fixed the tests for the Builder, but the Cache test will probably still fail. @phue do you maybe have an idea why this happens, I assume you...

> 91 files changed. This PR looks messed Yeah, this happened when I rebased this morning, I think the nextflow master branch changed? I can close and reopen a cleaner...

Thanks, I think it is back to what it should be now.

I realized that the previous commits did not handle cases where `$CH_IMAGE_STORAGE` was unset. This is better now. My problem is that I do not know how to properly adapt...

I have explored the reason for the failing tests some more locally. **Builder** `should get run command` and `should get the ch-run command line` I think the builder test fail...

#3566 is not fixed by my changes. This still leads to a `java.nio.channels.OverlappingFileLockException` I assume that this relates to `nextflow.file.FileMutex`. I assume that multiple processes manage to lock the file,...

I am unable to come up with a solution using a lock file. However, what seems to work well in my tests is simply waiting and retrying if the pull...

I have now added in optional squashfs (useSquash) image support for the process-specific image. Since I have no squashfs compatible system I cant test this, but it is a very...