-
Notifications
You must be signed in to change notification settings - Fork 465
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
fix(jobs): use new docker image #2945
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't remember why jobs is not yet using the unified image. Do you remember? @bodinsamuel
@@ -91,12 +91,15 @@ RUN true \ | |||
&& apt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false | |||
|
|||
# Do not use root to run the app | |||
USER node | |||
# BUT it does not work with secret mount (could not find a solution yet) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when do we need secret mount?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To load Google credentials for bigquery
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need to find a solution before merging this change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nope, just running as root is good, <i just left the comment to be sure the next person is not trying to put an user back
No big reasons, it was just a matter of taking the time |
Describe your changes
Already deployed in staging, nb: requires manual change before deployment on prod