When someone runs the quip stack, all files that are created on host machine, to be created as user.
Some of the docker containers seem to be OK to be run as user (eg. quip-findapi), while others need to be worked with to sort out the details. (eg. quip-loader, at the moment can't open run.sh as non-root, and so the container cannot start as non-root. Need to work out fixes to problems like this one).
birm
commented
5 years ago
When someone runs the quip stack, all files that are created on host machine, to be created as user.
Some of the docker containers seem to be OK to be run as user (eg. quip-findapi), while others need to be worked with to sort out the details. (eg. quip-loader, at the moment can't open run.sh as non-root, and so the container cannot start as non-root. Need to work out fixes to problems like this one).