Hmm, I guess kayobe thinks it is managing that container and you have an existing container with the same name. Kayobe is is doing: `state: absent`. I think you should be able to remove the seed from the docker-regsitry group to prevent this from happening:
Hmm, I guess kayobe thinks it is managing that container and you have an existing container with the same name. Kayobe is is doing: `state: absent`. I think you should be able to remove the seed from the docker-regsitry group to prevent this from happening:
https:/ /github. com/openstack/ kayobe/ blob/master/ etc/kayobe/ inventory/ groups# L77-L81
Change it to something like ((empty group):
[docker- registry]
I think the original idea was kayobe would clean up the container if you toggled docker_ registry_ enabled to false.