jupyterhub-deploy-docker | Reference deployment of JupyterHub with docker | Continuous Deployment library

by jupyterhub Python Version: Current License: BSD-3-Clause

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | jupyterhub-deploy-docker Summary

jupyterhub-deploy-docker is a Python library typically used in Devops, Continuous Deployment, Jupyter, Docker applications. jupyterhub-deploy-docker has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. However jupyterhub-deploy-docker build file is not available. You can download it from GitHub.

Key components of this reference deployment are:.

Support

Quality

Security

License

Reuse

Support

jupyterhub-deploy-docker has a low active ecosystem.

It has 584 star(s) with 340 fork(s). There are 37 watchers for this library.

It had no major release in the last 6 months.

There are 0 open issues and 71 have been closed. On average issues are closed in 1515 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of jupyterhub-deploy-docker is current.

Quality

jupyterhub-deploy-docker has 0 bugs and 0 code smells.

Security

jupyterhub-deploy-docker has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

jupyterhub-deploy-docker code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

jupyterhub-deploy-docker is licensed under the BSD-3-Clause License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

jupyterhub-deploy-docker releases are not available. You will need to build from source code and install.

jupyterhub-deploy-docker has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of jupyterhub-deploy-docker

Get all kandi verified functions for this library.

jupyterhub-deploy-docker Key Features

No Key Features are available at this moment for jupyterhub-deploy-docker.

jupyterhub-deploy-docker Examples and Code Snippets

No Code Snippets are available at this moment for jupyterhub-deploy-docker.

Community Discussions

Trending Discussions on jupyterhub-deploy-docker

JupyterHub use logout does not stop docker container

How do I make jupyter-hub access my private docker image repository?

jupyterhub in docker container not able to connect to external directory

QUESTION

JupyterHub use logout does not stop docker container

Asked 2020-Feb-12 at 11:31

I successfully configured jupyterhub on google cloud using very basic DummyAuthenticator and Docker Spawner following this tutorial: https://github.com/jupyterhub/jupyterhub-deploy-docker Everything is ok, but when the user logouts its docker container is still running. I was expecting that the container will be stopped when it is unused. It is a waste of resources for my taste. Is there any chance to trigger that behavior?

...

ANSWER

Answered 2019-Feb-06 at 10:38

I don't think JupyterHub automatically deletes any services just by logging out.

But you can use Cull-Idle. It provides a script to cull and shut down idle single-user notebook servers. And its pretty easy to use.

Link :

https://github.com/jupyterhub/jupyterhub/tree/master/examples/cull-idle

Source https://stackoverflow.com/questions/54540313

QUESTION

How do I make jupyter-hub access my private docker image repository?

Asked 2019-May-17 at 09:44

I want to deploy my own image on JuPyter-hub. However, I need to deploy it to some registry so that the image puller of JHub can pull it from there. In my case, the registry is private. Although I am able to push the image to my registry, I don't know how will I make the jupyterhub release and deployment be able to pull the image.

I tried reading this doc (https://github.com/jupyterhub/jupyterhub-deploy-docker) but it could not help me understand how am I to add authentication in the jupyter hub deployment.

I deploy jhub with this command:

...

ANSWER

Answered 2019-May-17 at 09:44

Image pull secret can be used to pull a image from private registry.

Append the jupyter-hub-config.yam with the following blob.

Source https://stackoverflow.com/questions/56182317

QUESTION

jupyterhub in docker container not able to connect to external directory

Asked 2018-Jul-15 at 16:55

I am setting up a jupyterhub for users in our group to be able to run scripts using our python package on common data without having to install the environment on their computers. The system is based on jupyterhub-deploy-docker (https://github.com/jupyterhub/jupyterhub-deploy-docker/) with the modifications for running on a localhost (https://github.com/PHI-Toolkit/jupyterhub-deploy-docker-localhost) which spawns Docker Containers with single user jupyter notebook instances from a dockerized jupyterhub. The idea is to mount a local host directory (or that of a data server) into the jupyterhub container and from there feed it through to the single user instances, to be used as notebook_dir. Then, ipynbs can access the data on the server and be saved there.

The whole approach works well when not dockerized (for testing, authentifying with DummyAuthenticator and spawning with SimpleLocalProcessSpawner), but I can't get the docker containers to see the host directory. My approach is to additionally bind the path on the host machine and specify the used DOCKER_NOTEBOOK_DIR as a target. Therefore, in docker-compose.yml I alter the volumes section

...

ANSWER

Answered 2018-Jul-15 at 16:55

Looking into the documentation and code often helps. I got it to work:

In the dockerspawner source code https://github.com/jupyterhub/dockerspawner/blob/master/dockerspawner/dockerspawner.py#L218 the option of mounting host file/directory into container (however the description was not detailed enough for me to understand how. To that end, the tests were helpful: https://github.com/jupyterhub/dockerspawner/blob/3906f4bebc92b383c73fb8d06c58a7c57003939a/tests/volumes_test.py#L25 suggests that specifying

Source https://stackoverflow.com/questions/51330356

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install jupyterhub-deploy-docker

This deployment uses GitHub OAuth to authenticate users.
setting the GITHUB_CLIENT_ID, GITHUB_CLIENT_SECRET, and OAUTH_CALLBACK_URL environment variables when you run the JupyterHub container, or
add them to an oauth.env file in the secrets directory of this repository. You may need to create both the secrets directory and the oauth.env file. For example, add the following lines in the oauth.env file: oauth.env file GITHUB_CLIENT_ID=<github_client_id> GITHUB_CLIENT_SECRET=<github_client_secret> OAUTH_CALLBACK_URL=https://<myhost.mydomain>/hub/oauth_callback Note: The oauth.env file is a special file that Docker Compose uses to lookup environment variables. If you choose to place the GitHub OAuth application settings in this file, you should make sure that the file remains private (be careful to not commit the oauth.env file with these secrets to source control).
Finish configuring JupyterHub and then build the hub's Docker image. (We'll build the Jupyter Notebook image in the next section.).
Configure userlist: Create a userlist file of authorized JupyterHub users. The list should contain GitHub usernames, and this file should designate at least one admin user. For instance, the example file below contains three users, jtyberg, jenny, and guido, and one designated administrator, jtyberg: userlist file jtyberg admin jenny guido The admin user will have the ability to add more users through JupyterHub's admin console.
Use docker-compose to build the JupyterHub Docker image on the active Docker machine host by running the make build command: make build

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: