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

Failure to schedule task: the container name is already in use by container #24940

Open
gscho opened this issue Jan 24, 2025 · 0 comments
Open
Labels

Comments

@gscho
Copy link

gscho commented Jan 24, 2025

Nomad version

v1.9.5 but was happening with v1.9.1. Also this never happens on windows and those hosts are running v1.7.7

Docker version

Docker version 27.5.1, build 9f9e405

Operating system and Environment details

22.04.5 LTS (Jammy Jellyfish)

Issue

Jobs fail intermittently with:

failed to create container: Error response from daemon: Conflict. The container name "/build-6cc59855-66d6-6db4-9e87-0e3a6c669e88" is already in use by container "e0c1fd8704656777b88eb06bd01637e348ee1909dcb6c2384a6ad849f8b8b9cb". You have to remove (or rename) that container to be able to reuse that name.

Seems to be the same as an older issue: #2084

Reproduction steps

Unclear. We run hundreds or thousands of batch jobs per day and an unknown percentage of them fail with this error.

Image

@gscho gscho added the type/bug label Jan 24, 2025
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