Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem stopping/removing old container. realm is not identified correctly #380

Closed
stefanoborini opened this issue Mar 29, 2017 · 0 comments
Labels
Milestone

Comments

@stefanoborini
Copy link
Contributor

stefanoborini commented Mar 29, 2017

With the following situation (note that the containers are already stopped):

(venv) sborini@MacBook-Pro:jupyterhub (369-google-analytics) [25 stash] $ docker ps -a
CONTAINER ID        IMAGE                                   COMMAND                  CREATED             STATUS                      PORTS                     NAMES
3377349fe8fa        simphonyproject/filemanager             "/startup.sh"            42 hours ago        Exited (255) 38 hours ago   0.0.0.0:32769->8888/tcp   remoteexec-test-36eb77743ba748a6be537b7bef8bad01
418bfeb791e6        simphonyproject/simphony-ui:0.1.0       "/startup.sh"            43 hours ago        Exited (255) 38 hours ago   0.0.0.0:32768->8888/tcp   remoteexec-test-2cf0aebe6bbc49a9867f7193b02b167d
2a539f8fc681        simphonyproject/simphony-mayavi:0.6.0   "/startup.sh"            4 weeks ago         Exited (255) 4 weeks ago    0.0.0.0:32772->8888/tcp   remoteexec-test-de65152627e048ee9c274697bec506c0

I obtain these logs when trying to restart the container

[I 2017-03-29 10:37:08.983 JupyterHub log:100] 200 GET /hub/api/authorizations/cookie/jupyter-hub-token-test/[secret] ([email protected]) 10.96ms
[I 170329 10:37:08 container_manager:297] Got container image: simphonyproject/simphony-mayavi:0.6.0
[I 170329 10:37:08 container_manager:311] Container for image simphonyproject/simphony-mayavi:0.6.0 already present. Stopping.
[I 170329 10:37:08 container_manager:528] Stopping container 2a539f8fc6817b58d0f2f0b783dbaa7364cbba84a24ad247e9987a5369894d18
[E 170329 10:37:09 container_manager:544] Container 2a539f8fc6817b58d0f2f0b783dbaa7364cbba84a24ad247e9987a5369894d18 belongs to realm  instead of remoteexec. Refusing to stop.
[I 170329 10:37:09 container_manager:339] Mounting these volumes: 
    /tmp/remoteapp/test -> /workspace
[E 170329 10:37:09 container:270] Unhandled error starting test's container: 409 Client Error: Conflict ("b'{"message":"Conflict. The container name \\"/remoteexec-test-de65152627e048ee9c274697bec506c0\\" is already in use by container 2a539f8fc6817b58d0f2f0b783dbaa7364cbba84a24ad247e9987a5369894d18. You have to remove (or rename) that container to be able to reuse that name."}'")
[E 170329 10:37:09 web:1946] 500 POST /user/test/api/v1/containers/ (127.0.0.1) 51.33ms

I suspect those containers are residues of a stop. The code should be able to deal with them, but apparently at inspect there's something broken with the realm extraction when the container is stopped. Different format?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant