-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Nomad does not handle container names conflict #3419
Comments
Something similar is described in #629 |
I suppose that docker driver should detect:
.. and marks node as "problem" with the following migration of all tasks to another node. |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
Nomad v0.6.3
Operating system and Environment details
CentOS Linux release 7.4.1708 (Core)
Docker:
Version: 17.09.0-ce
API version: 1.32 (minimum version 1.12)
Go version: go1.8.3
Git commit: afdb6d4
Built: Tue Sep 26 22:42:49 2017
OS/Arch: linux/amd64
Experimental: false
Issue
Nomad does not handle container names conflict and marks tasks as dead instead of migrating to another client.
Nomad Client logs
Event log of allocation:
Expected result
Nomad handles the issue and migrates task with allocation directory to another cluster node.
The text was updated successfully, but these errors were encountered: