-
Notifications
You must be signed in to change notification settings - Fork 683
Issue using non-root user with google-batch executor #4880
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
Comments
Mino type, not sure if it's what you actually tried: process { containerOptions = "-u 1000:1000" } |
Likely need to look at the GCS mount options to see if there is anything related to permissions: nextflow/plugins/nf-google/src/main/nextflow/cloud/google/batch/GoogleBatchScriptLauncher.groovy Lines 126 to 142 in fd27fbc
If you can submit a job through |
So far I've had success with the following but it fails when allow_other is removed.
|
Revisiting this one year later with a proposed fix, thanks in advance for any reviews or guidance! |
Bug report
Expected behavior and actual behavior
The GCP Batch executor (
google-batch
) should allow non-root users for improved security concerns. Today, only the root user can access files under/mnt/disks/**
Steps to reproduce the problem
I have pushed two public docker images, one with
root
as the default user, another withworker
as the default user.These can be found at on dockerhub at:
The workflow I am running is as follows
main.nf:
nextflow.config:
Program output
The execution is successful in the root image, while the non-root image gives the following error in the GCP Batch logs:
nextflow.log
Additionally, running

gcloud beta batch jobs describe projects/<project-id>/locations/us-west1/jobs/<my-nf-job> --format json
gives a consistent output like:Environment
Additional context
Other attempts to address the issue
process { containerOptions = "--user worker" }
process { containerOptions = "--u 1000:1000" }
(worker's user/group id)I am wondering if there's a need for an explicit option like the docker executor's fixOwnership
The text was updated successfully, but these errors were encountered: