-
Notifications
You must be signed in to change notification settings - Fork 6
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
fix: Mount /dev/shm to the correct container. #1984
Conversation
b85d1e1
to
73d7a0f
Compare
You can access the deployment of this PR at https://renku-ci-nb-1984.dev.renku.ch |
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.
Thanks Alessandro. One suggestion to make sure that things are ok if memory is None.
Thanks, I've included your change. |
I absolutely agree. The new version of amalthea does not have patches like this at all. So when we retire the old version this code will just be thrown out. |
Currently container #1 is `oauth-proxy` while JupyterServer, is #0. Additionally use half of the memory requested by the pod instead of half of the storage. Since we rely on memory there is no need to tie the increased /dev/shm to requesting storage in the session. NOTE: This system of patching the manifest is very brittle and the bug being fixed by this commit might appear again as soon as the containers sorting changes. We should think about a different way of interacting with the manifests of the user-sessions.
08bab41
to
24740fc
Compare
Migrating SwissDataScienceCenter/renku-notebooks#1984 Co-authored-by: Alessandro Degano <alessandro.degano@epfl.ch>
Currently container #1 is
oauth-proxy
while JupyterServer, is #0.Additionally use half of the memory requested by the pod instead of half of the storage.
Since we rely on memory there is no need to tie the increased /dev/shm to requesting storage in the session.
NOTE: This system of patching the manifest is very brittle and the bug being fixed by this commit might appear again as soon as the containers sorting changes. We should think about a different way of interacting with the manifests of the user-sessions.
/deploy renku=leafty/fix-renku-jupyterserver