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

Upgrade Jupyter-server-proxy #46

Closed
3 tasks done
wildintellect opened this issue Mar 20, 2024 · 6 comments
Closed
3 tasks done

Upgrade Jupyter-server-proxy #46

wildintellect opened this issue Mar 20, 2024 · 6 comments
Assignees

Comments

@wildintellect
Copy link
Collaborator

wildintellect commented Mar 20, 2024

A fix has been released for a vulnerability in Jupyter-server-proxy, 2i2c has mitigations in place, however it's best practices that we update to non-vulnerable versions of packages.

jupyter-server-proxy >= 4.1.1 or 3.2.3 https://github.com/jupyterhub/jupyter-server-proxy/pull/465/files

Upgrade pattern should follow #41

Tasks

Preview Give feedback
@wildintellect
Copy link
Collaborator Author

wildintellect commented Mar 20, 2024

@abarciauskas-bgse
Copy link
Contributor

abarciauskas-bgse commented Mar 20, 2024

Our last procedure to upgrade the pangeo-notebook image was:

Checklist:

@wildintellect
Copy link
Collaborator Author

Best I can tell Rocker being tagged to 4.3 is also recent and likely patched https://hub.docker.com/r/rocker/binder/tags

@batpad
Copy link
Collaborator

batpad commented Mar 21, 2024

PR to 2i2c infra repo to update the singleuser image at 2i2c-org/infrastructure#3823

@wildintellect
Copy link
Collaborator Author

I've confirmed in both VEDA and GHG hubs the new image is deployed - had to login and check the conda list proxy version is at 4.1.2

TODO: make it easier to tell what container image is being run, maybe there's an easy command but it's not obvious.

@batpad
Copy link
Collaborator

batpad commented Mar 26, 2024

@wildintellect there will be an environment variable called JUPYTER_IMAGE that one can check in a notebook / on the container. Should we document this somewhere?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants