-
Notifications
You must be signed in to change notification settings - Fork 192
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
Docker UID Defaults #336
Comments
Also, most of the clusters are cunning CentOS which requires |
Do you guys use Docker on a cluster? We cannot do that for "security reasons" here. Also, does that then work for everyone? I know that the fixOwnership and runOptions stuff will work pretty much everywhere (?) while the mountFlags might not (?) |
We have isolated cluster where we have a docker. We are using local executor and the only way to actually run it correctly (CentOS security policy) I had to enable the mountFlags to |
I don't think that it should go in the template base config unless it works for everyone (at least, doesn't break stuff for those that don't need it). But why does nextflow itself not have these as defaults if that's the case? |
Good question - @pditommaso can you share some insights on why this is not the "default" behaviour? |
Good point, that was planned nextflow-io/nextflow#515. It was never merged because it could introduce a breaking change caused by the fact that Maybe it's time to give it a try. |
This causes problem when running Spark in Docker. |
|
I think not no |
How important is it to keep this |
I never had issues without it - so maybe it’s not required. We had people who had to use it though, which is something we should document / state in troubleshooting on the webpage maybe ? |
Anyhow, I'll be removing that for Sarek, I'll keep everyone updated if any issue arise. |
We should probably think about adding this here as default to the Docker scope:
The text was updated successfully, but these errors were encountered: