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.

Sign up for GitHub

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

Jump to bottom

User inside Notebook is root and not jovyan #2602

Closed
kimwnasptd opened this issue Mar 1, 2019 · 11 comments
Closed

User inside Notebook is root and not jovyan #2602

kimwnasptd opened this issue Mar 1, 2019 · 11 comments
Labels
area/jupyter Issues related to Jupyter cuj/build-train-deploy priority/p0
Projects
0.5.0

Comments

@kimwnasptd
Copy link
Member

Tested on latest master with image gcr.io/kubeflow-images-public/tensorflow-1.10.1-notebook-cpu:v-base-0524257-1200. If I open a new terminal in the notebook, then I am user root and not jovyan.

/cc @jlewi @zabbasi
@lluunn lluunn added the area/jupyter Issues related to Jupyter label Mar 2, 2019
@jlewi jlewi added this to New in 0.5.0 via automation Mar 4, 2019
@jlewi jlewi moved this from New to Build / Train / Deploy from notebook in 0.5.0 Mar 4, 2019
@zabbasi
Copy link
Contributor

zabbasi commented Mar 4, 2019 •
edited

@kimwnasptd How come? can you please elaborate.
notebook-dir is already set in Dockerfile
Also tested one of the images one more time (gcr.io/kubeflow-images-public/tensorflow-1.12.0-notebook-cpu:v-base-97b94c0-1202) by mounting a sample file in /home/jovyan. When notebook is launched my sample file showed up in the jupyter list of files

docker run -v test.ipynb:/home/jovyan/test.ipynb  -it -p 8888:8888 gcr.io/kubeflow-images-public/tensorflow-1.10.1-notebook-cpu:v-base-97b94c0-1202

@zabbasi
Copy link
Contributor

zabbasi commented Mar 6, 2019

/close

@k8s-ci-robot
Copy link
Contributor

@zabbasi: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

0.5.0 automation moved this from Build / Train / Deploy from notebook to Done Mar 6, 2019
@zabbasi
Copy link
Contributor

zabbasi commented Apr 1, 2019

/open

@zabbasi
Copy link
Contributor

zabbasi commented Apr 1, 2019

@jlewi

@zabbasi
Copy link
Contributor

zabbasi commented Apr 1, 2019

/label priority/p0

@jlewi jlewi reopened this Apr 1, 2019
0.5.0 automation moved this from Done to New Apr 1, 2019
@jlewi
Copy link
Contributor

jlewi commented Apr 1, 2019

/label priority/p0

@jlewi
Copy link
Contributor

jlewi commented Apr 1, 2019

/priority p0

@zabbasi zabbasi mentioned this issue Apr 2, 2019
Merged
@zabbasi
Copy link
Contributor

zabbasi commented Apr 2, 2019

Hold for postsubmit test to run so that all the recently released images are tagged to v0.5.0.

@zabbasi
Copy link
Contributor

zabbasi commented Apr 3, 2019

/close

0.5.0 automation moved this from New to Done Apr 3, 2019
@k8s-ci-robot
Copy link
Contributor

@zabbasi: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/jupyter Issues related to Jupyter cuj/build-train-deploy priority/p0
Projects
No open projects
0.5.0
  
Done
Milestone
No milestone
Development

No branches or pull requests
5 participants
@jlewi @zabbasi @kimwnasptd @k8s-ci-robot @lluunn