Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

503 proxy target error #177

Open
anaderi opened this Issue Dec 5, 2016 · 0 comments

Comments

Projects
None yet
2 participants
Owner

anaderi commented Dec 5, 2016

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.

malchun was assigned by anaderi Dec 5, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment