-
Notifications
You must be signed in to change notification settings - Fork 803
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
Give notebook containers elevated privileges #379
Comments
Try the following (using a v0.6.0- chart) hub:
extraConfig: |
from kubernetes import client
def modify_pod_hook(spawner, pod):
pod.spec.containers[0].security_context = client.V1SecurityContext(
privileged=True,
capabilities=client.V1Capabilities(
add=['SYS_ADMIN']
)
)
return pod
c.KubeSpawner.modify_pod_hook = modify_pod_hook
singleuser:
uid: 0
gid: 0
storage:
extraVolumes:
- name: fuse
hostPath:
- path: /dev/fuse
extraVolumeMounts:
- name: fuse
mountPath: /dev/fuse
|
OK, I've given this a shot and I'm now getting 500 errors. What is the right way to diagnose this? |
Where are you getting 500 from? Logs would be useful!
…On Fri, Jan 5, 2018 at 12:12 PM, Matthew Rocklin ***@***.***> wrote:
OK, I've given this a shot and I'm now getting 500 errors. What is the
right way to diagnose this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#379 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAB23jn0ygUoOZCaShWvqCwpBJxD4WNIks5tHoIzgaJpZM4RUtye>
.
--
Yuvi Panda T
http://yuvi.in/blog
|
Directly after trying to log in.
Logs
|
@mrocklin looks like the error is in: extraVolumes:
- name: fuse
hostPath:
- path: /dev/fuse Specifically, the '-' before the last line. Can you replace with: extraVolumes:
- name: fuse
hostPath:
path: /dev/fuse and try? |
Still failing
|
logs from the hub
|
We spent some more time and figured it all out :) |
It was the singleuser.cmd, which we default to jupyterhub-singleuser. It needed to be set to start.sh instead I believe. |
If anyone comes across this issue in the future, I've created a jupyter image and a helm config fragment for mounting GCS storage via fuse here: https://github.com/noahhomes/r-mkl-notebook |
Hi,
I would like to use a FUSE file system in my containers. To do this locally it seems that I need to pass the
/dev/fuse
device to the docker container and run it with elevated permissions. Locally I do the following:Is there a way for me to specify these flags in my config.yaml file?
The text was updated successfully, but these errors were encountered: