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

Feature: start.sh jupyter lab --secured-env #728

Closed
taqtiqa-mark opened this issue Oct 17, 2018 · 1 comment

Comments

@taqtiqa-mark
Copy link
Contributor

@taqtiqa-mark taqtiqa-mark commented Oct 17, 2018

Hi,
Thank you for all the effort making the Jupyter Docker Stacks.

The default security is very good.

There are use cases, encouraged by containers, where the jupyter container and the system it runs within, lie inside the security boundary.

In these use cases it is convenient to have a command line option to launch the server without password or token.

Currently my chef recipe launches jupyter lab as follows:

docker_container 'jupyter-datascience' do
  repo 'jupyter/datascience-notebook'
  tag '1145fb1198b2'
  port '80:8888'
  env 'JUPYTER_ENABLE_LAB=yes'
  volumes [ "/home/#{node[:user][:username]}/work:/home/jovyan/work" ]
  command 'start.sh jupyter lab'
  action :run
end

It would be useful to launch the jupyter lab container with no password and no token by:

start.sh jupyter lab --secured-env

@taqtiqa-mark

This comment has been minimized.

Copy link
Contributor Author

@taqtiqa-mark taqtiqa-mark commented Oct 19, 2018

Hmm, it is possible that this issue could be closed as implemented with a documentation PR describing the use case and the suggestion to the following effect:

start.sh jupyter lab --LabApp.token=''

ericdill added a commit to ericdill/docker-stacks that referenced this issue Oct 23, 2018
@parente parente closed this in #734 Oct 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.