You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it may be caused by the reason that container has been removed (by docker or culling) but the record of it running inside everware is still present. Even after logout by /hub/logout, and subsequent login user get 500 error (cannot access container).
The only workaround now is - to create container named 'jupyter-user' like (docker-swarm run -ti --name jupyter-anaderi busybox) and then stop it by admin-panel.
The desired behaviour should be - if everware cannot get container it is supposed to run, it should do the cleanup and offer prompt for creation of a new one.
The text was updated successfully, but these errors were encountered:
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 everware is still present. Even after logout by /hub/logout, and subsequent login user get 500 error (cannot access container).
The only workaround now is - to create container named 'jupyter-user' like (
docker-swarm run -ti --name jupyter-anaderi busybox
) and then stop it by admin-panel.The desired behaviour should be - if everware cannot get container it is supposed to run, it should do the cleanup and offer prompt for creation of a new one.
The text was updated successfully, but these errors were encountered: