Skip to content
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.

ignite rm -f fails to remove the container #306

Closed
luxas opened this issue Aug 9, 2019 · 1 comment · Fixed by #320
Closed

ignite rm -f fails to remove the container #306

luxas opened this issue Aug 9, 2019 · 1 comment · Fixed by #320
Assignees
@twelho
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v0.5.0

Comments

@luxas
Copy link
Contributor

luxas commented Aug 9, 2019

Due to a race condition in the docker container implementation:

ignite rm -f f4c3114f94acafe1
FATA[0000] failed to remove container for VM "f4c3114f94acafe1": Error response from daemon: removal of container b78b8fe5e7997852445248b24c213a261ab1becae96725db073b8b4c54d37c05 is already in progress

cc @twelho
@luxas luxas added this to the v0.5.0 milestone Aug 9, 2019
@luxas luxas added kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Aug 9, 2019
@twelho
Copy link
Contributor

twelho commented Aug 12, 2019 •
edited
Loading

Was the VM running when issuing rm -f? If so, it's probably an issue with waitForContainer in the Docker client. I'll look into it now.

@twelho twelho mentioned this issue Aug 12, 2019
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@twelho twelho

Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v0.5.0
Development

Successfully merging a pull request may close this issue.

Fix ignite rm -f for a running VM without --debug twelho/ignite
2 participants
@luxas @twelho