204 issues in everware/everware
unable to start everware if user's container is running since the last run of the everware
scenario: 1. run everware 2. user logs in and runs container 3. stop everware, remove jupyterhub.sqlite 4. start everware again it fails: [D 2017-07-06 10:26:28.867 Everware spawner:458] Container ...
-
Opened by anaderi
Jul 6, 2017 - 1 comment
Bring Your Own Resources
The branch adds a brand-new feature which allows to use custom servers for running containers.
-
Opened by StrausMG
Jun 20, 2017 - 12 comments
Incorrect number of active containers on /hub/stats
The figure is always shown as 0. The reason is in the usage of wrong docker client in the handler of the page.
-
Opened by StrausMG
Jun 17, 2017
new url for displaying statistics
The PR adds a new page '/hub/stats' for displaying statistics on the machine that everware is running on. Currently two figures are available: 1. the number of currently running containers 2. ...
-
Opened by StrausMG
May 20, 2017 - 1 comment
do not toggle 'build log' button upon build error if log is already shown
currently upon build error 'build log' button is toggled. which is fine unless user already reads the log. so it should not change button state if error has occurred and the button was ON.
-
Opened by anaderi
May 19, 2017
Saving states via images
Users will be able save theirs current states and restore them later using special link.
-
Opened by vchagaev
May 16, 2017 - 13 comments
Allow to kill stuck builds
My container build has stuck, probably waiting for a confirmation that will never come. An I can't do anything - when I try to spawn from another repository, it brings me tho the same stuck build. ...
-
Opened by kazeevn
May 5, 2017 - 1 comment
Minor fixes
Remove repeated wait_up, always try to build an image (there was a block in __enter__), return ip, port from swarm spawner as jupyterhub requires
-
Opened by astiunov
Apr 13, 2017