Closed trenta closed 4 years ago
Hi,
Can you specify more about your system configuration (OS, docker version etc.)?
I'm quite new to Docker myself, but I will try to look it up.
Best,
Shalom Hillel Roth
Hi,
Thanks for the reply. We are running Ubuntu 18.04 with Docker version 19.03.1, build 74b1e89
No matter what user flag we use the output folder structure is owned by root. I’ve tried with both -u and —user. With static UID and GID entries to make sure it wasn’t the variables calling them.
Cheers
Trent
On 6 Nov 2019, at 3:56 am, shalomhillelroth notifications@github.com wrote:
Hi,
Can you specify more about your system configuration (OS, docker version etc.)?
I'm quite new to Docker myself, but I will try to look it up.
Best,
Shalom Hillel Roth
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/a2iEditing/RNAEditingIndexer/issues/7?email_source=notifications&email_token=AANUMK6OSOELPASZJOX56RTQSGQTDA5CNFSM4JIO5GZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDDN2QY#issuecomment-549903683, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANUMK3SW7SUXK32HEH66MTQSGQTDANCNFSM4JIO5GZQ.
Closing issues as the problem was on my end. The issue occurs when the directory structure doesn't already exist. It gets created as the root user. If the directory structure already exists this problem doesn't.
We have tried running this following the instructions on running as user: -u $(id -u ${USER}):$(id -g ${USER})
The output folder structure is still written as root.
I've tried using static uid and gid as a test and got the same results.