Re: [bids-discussion] bids-apps - file permissions of produced artifacts

7 views
Skip to first unread message

Chris Gorgolewski

unread,
Mar 14, 2017, 3:11:34 PM3/14/17
to bids-discussion, bids-apps-dev
Hi,

To clarify - you are talking about running BIDS Apps with Docker right?

You can override the internal user name used by Docker from the command line. See: https://docs.docker.com/engine/reference/run/#user (I have not tried it, but it should do the trick).

Best,
Chris

PS Does this mean you have a multi-tenant system with Docker access for non-privileged users?
PPS You can convert any BIDS App to singularity for your users with docker2singularity (but I'm sure you are aware of this...)

On Tue, Mar 14, 2017 at 12:03 PM, Yaroslav Halchenko <yarik...@gmail.com> wrote:
Dear BIDS-App experts,

Before all bids-apps become available as singularity containers --
is there any  workflow/workaround (chmod g+s outputs, umask, ... some
other collection of steps without requiring actual root access) to get
results of the BIDS-app operation to be owned by originating user and
not root?

Having produced results owned by root really hinders utility of any
BIDS-app by regular mortals AKA users.

Thanks in advance for the clarification!
--
Yaroslav O. Halchenko
Center for Open Neuroscience     http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834                       Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

--
You received this message because you are subscribed to the Google Groups "bids-discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bids-discussion+unsubscribe@googlegroups.com.
To post to this group, send email to bids-discussion@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bids-discussion/20170314190350.wvdytpwsd5iq3wah%40hopa.kiewit.dartmouth.edu.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages