Open jfear opened 8 years ago
Poking around a bit. If instead of using -u 1000:1000 I use 1:1 the lookup of the daemon user goes well and multiqc will run. However, I loose permissions to /opt/lcdb (ie #1).
Ok, if I completely remove the -u option everything seems to work. I know that I am running as root when I don't add the -u, is there any disadvantage to running as root? /opt/lcdb is still mounted as your user name 1000:staff.
Disadvantage of running as root is having to clean up all the created files later as root. Just an inconvenience really.
Do you think allowing /opt/lcdb to be world-writeable in the dockerfile would solve the issue?
A similar problem here, solved with a clever method: http://stackoverflow.com/a/26547845
Kind of strange this problem doesn't pop up more. I'm thinking for local runs and testing we should use conda envs rather than docker. As long as the docker container uses the same conda env it should have the same results.
Keep running into docker issues, thought I would ask you first before spending too much time trouble shooting. Basically when I run multiqc I get the following:
This seems related to here. I still have issues with #1 but have been running directly as 1000:1000. Maybe I will fire up a linux VM next week and see if I can narrow it down to an OSX problem.
Anyways if you have not run into this before, I can trouble shoot. But, thought you may have seen this kind of thing before.