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

Notebook content is removed on every start stop #312

Closed
Barteus opened this issue Oct 25, 2023 · 1 comment
Closed

Notebook content is removed on every start stop #312

Barteus opened this issue Oct 25, 2023 · 1 comment

Comments

@Barteus
Copy link

Barteus commented Oct 25, 2023

Bug Description

When I create a notebook using the default notebook image - charmedkubeflow/jupyter-scipy:v1.7.0_20.04_1

New notebooks are created in the /var/lib/pebble/default instead of the volume that is attached to the Pod under /home/jovyan/

To Reproduce

  1. Deploy Kubeflow
  2. Create a notebook
  3. Open the notebook and create a new ipynb
  4. Stop the notebook and start it again
  5. File is missing

Expected: Files exists after notebook restart.

Environment

  • GCP VM
  • microk8s 1.24/stable
  • Kubeflow 1.7

Relevant log output

**Notebook**
$ !pwd
/var/lib/pebble/default

Additional context

No response

i-chvets pushed a commit that referenced this issue Nov 1, 2023
#312

Summary of changes:
- Updated Jupyter UI charm config to point to updated ROCKs.
kimwnasptd pushed a commit that referenced this issue Nov 16, 2023
* [KF-1471] fix: add default value for pipelines (#221)

* fix: add default value for pipelines
canonical/kfp-operators#159

Fixes #159 

Summary of changes:
- Added back default value for pipelines access.
- Added tests for default values of pipelines access and images for 1.7
  release.
- Modified code to check for mindspore image only not version.

---------

Co-authored-by: Andrew Scribner <[email protected]>

* fix: update ui charm config
#312

Summary of changes:
- Updated Jupyter UI charm config to point to updated ROCKs.

---------

Co-authored-by: Andrew Scribner <[email protected]>
@kimwnasptd
Copy link
Contributor

This is now fixed in the 1.7/stable bundle. The fix was introduced in
canonical/kubeflow-rocks#61
#314

We'll need to keep this in mind though when creating our ROCKs for 1.8

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

2 participants