-
-
Notifications
You must be signed in to change notification settings - Fork 462
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
[BUG] k3d-tools already in use by container #924
Comments
Hi @arkadius , thanks for opening this issue! |
Hi, thank you for taking a look into logs. Is it possible to have some kind of lock to ensure that tools node is created only once? |
I'll look into it as soon as I find the time 👍 |
Thanks in advance. I'll give this workaroud a try. Thanks 👍 |
i am getting the same error as well but this is different
Anyone know this issue please help |
@spowers4u which version of k3d are you using? |
Hi @iwilltry42, I got it sorted out thanks. In fact the underlying docker version was not compatible. It requires to be atleast >=20.02 |
From time to time, creation of cluster fail with message
Error response from daemon: Conflict. The container name "/k3d-k3s-default-tools" is already in use by container
It looks like
k3d-tools
is created twice. Second creation (for gathering environment information purpose) finishing with error. Any idea what happen? It looks likek3d-tools
is not reuesed or not cleaned up correctly after first creation.What did you do
k3d cluster create k3s-default --wait --config=single-cluster.yml --trace
single-cluster.yml
content:Nothing - just wait until command finishes
What did you expect to happen
Command will finish with error code 0 and k3d cluster is operating.
Screenshots or terminal output
Which OS & Architecture
Cluster was being created on github acitons workers. Job creating it: https://github.com/TouK/nussknacker/runs/4779179444?check_suite_focus=true
Os: Ubuntu 20.04.3 LTS Arch:x86_64
Which version of
k3d
Which version of docker
The text was updated successfully, but these errors were encountered: