-
Notifications
You must be signed in to change notification settings - Fork 4
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
PloverDB should run as user "user" in ITRB-deployed settings #2
Comments
uwsgi is run as |
Hmm, IDK. Is nginx running as root? |
Just checking back.... can we close out this issue? |
Maybe it would make sense to slack Kanna to ask b/f we close it out |
thanks for the reminder - good idea. will check in with Kanna. |
checked in with Kanna for more details - they want us to run all services as
because PloverDB uses a base image that handles users a certain way, this might get a little weird. but I'm sure is doable. |
This seems like an "After the Sept. 28 demo" kind of issue (though still worth doing, just on the longer term). |
NCATS DevOps is requesting that the PloverDB service not run as root, inside the container. It should run as a less-privileged user (and we should document the username in the README or Wiki).
The text was updated successfully, but these errors were encountered: