Andrey Ustyuzhanin
Andrey Ustyuzhanin
use same progress-wheel across all 'waiting' screens as at container 'starting' screen.
Once user decides to stop container, he/she goes to control panel, press 'stop', and looks at message 'stopping container' that doesn't disappear itself - one has to refresh page manually...
needs investigation
as user gets 503 proxy target error it may be caused by the reason that container has been removed (by docker or culling) but the record of it running inside...
display - number of running containers - running since (date) - number of images built since start available under /status URL prefix
since v 0.7 jupyterhub can run services (https://github.com/jupyterhub/jupyterhub/blob/798346dbe8c9492f32cb7ceea7c6dffe635a85e4/docs/source/services.md) add parameter to everware config on how long everware should wait before shutting idle container down. Everware should run culling service to...
Usecase: user spawns a container from OpenML platform. in order to submit results back, he has to supply a special user-specific key. Such key could be entered manually in the...
If everware has cloned repo belonging to organization on behalf of user from this organization it might be perfectly OK to push to this repo. In other words everware should...
in case of slow start of quick shutdown of the container user might get 502 (bad gateway) error due to configurable-http-proxy isn't pointing to properly working instance.
otherwise users have been using everware before restart get 500 error.