Docker backend: implement a chown workaround after task execution

[peterhuene]

Currently files created by a container in the Docker backend will be created as root on systems where the docker daemon is running as root.

This leaves files in the output directory that cannot be removed by the user unless they elevate their privileges.

miniwdl solves this with a workaround where a special container is executed to chown the working directory contents to the user; as the container is also run as root, it doesn't require the user executing miniwdl to elevate their privileges.

We should consider implementing a similar workaround.

[thedeeppp]

Hey, I would like to work on this issue. might need a little help.

[ashug06]

Hi! I’m Ashutosh Goyal, and I’m interested in contributing to this project. I’d love to take up this issue. Could you please assign it to me?

[blenbot]

Hello! I tried to analyze the codebase and got hold off it mostly as well as miniwdl's workaround and came up with a solution to include post execution cleanup container mounting the folders in the container after each run of main containers and lastly change the ownership in the cleanup, let me know what you think, I have already started working on this and I would be really glad if you could assign me this issue. I was thinking of making minimal changes to crankshaftbackend class, thanks!