Skip to content
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

bump dind image to 18.09.2 #795

Merged
merged 1 commit into from
Feb 20, 2019
Merged

Conversation

minrk
Copy link
Member

@minrk minrk commented Feb 20, 2019

for CVE-2019-5736

users don't appear to be affected since we run them as uid 1000 and the vulnerability appears to require pods to run as uid 0

@yuvipanda
Copy link
Collaborator

@minrk users can still run as uid0 during the docker build itself, so we should still deploy this.

@yuvipanda
Copy link
Collaborator

Ah, I think I'm saying the same thing you're saying!

@minrk
Copy link
Member Author

minrk commented Feb 20, 2019

Yup, I could have been clearer. For "users" I meant jupyterhub user pods ("launches" I guess in Binder terms), so only builds were affected.

This was already deployed to mybinder.org: jupyterhub/mybinder.org-deploy#899 this PR only changes the default for binderhub.

@yuvipanda yuvipanda merged commit cc9bfae into jupyterhub:master Feb 20, 2019
@yuvipanda
Copy link
Collaborator

Awesome, thanks @minrk

yuvipanda pushed a commit to jupyterhub/helm-chart that referenced this pull request Feb 20, 2019
@choldgraf choldgraf added the maintenance Under the hood improvements and fixes label Oct 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Under the hood improvements and fixes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants