-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Permissions error writing cwl.outputs.json
when running with Docker
#325
Comments
In core.properties, if executor.set_permissions parameter is true, after execution Bunny chown all files in working directory to executor.permission.gid and executor.permission.uid or try to find uid and gid of current user. Can you try to set executor.permission.gid and executor.permission.uid in config? Maybe for some reason gid and uid are not detected properly, and that is why it failed. On which operating system you run workflow? |
Thanks so much, swapping the config over to As a more general question, is there a way to adjust the parameters via the command line without writing a new configuration directory/file -- via |
The latest version (1.0.3) of rabix cli doesn't use any additional containers for setting permissions so you can leave executor.set_permissions=true and nothing will happen in the case of local execution. We are also looking into a rework of the configuration system. |
- rabix-bunny: Update to 1.0.3 to avoid permissions errors rabix/bunny#325 - ericscript: Avoid rebuilding bwa indices during runs bcbio/bcbio-nextgen#2147 - arvados-cwl-runner: pin runtime to correct version of cwltool
Milso, thanks so much for working on this. I was testing 1.0.3 and ran into a separate issue (#383) but will definitely do more testing on this once that's resolved. Thanks again for all the help. |
While testing the latest bcbio test CWL workflow (https://github.com/bcbio/test_bcbio_cwl) using the 1.0.1 release, I'm running into a permissions issue using a Docker container. Everything runs cleanly when using
--no-container
but when I run with analysis happening in a container I get a mix of root and user owned files:which triggers an error writing/reading
cwl.outputs.json
for all steps in the pipeline:Thanks much for any suggestions/tips about how best to run this to avoid the issues. Ideally Docker would get run using
-u
so they're owned by the user and we never have to deal with root permissions outside of the container, but open to any ideas/thoughts about how best to do it. Thanks much.The text was updated successfully, but these errors were encountered: