Comment 5 for bug 2007142

It seems like you're discussing an issue related to Zun, specifically regarding the use of kuryr-libnetwork, the --cluster-store option, and a workaround involving pinning an older version of Docker. Additionally, there's mention of a long-term solution to migrate to containerd with the CNI network model. Here's a breakdown of the information by https://openingtoclosehours.com/:

Issue Summary:

Problem: Zun is dependent on kuryr-libnetwork, which relies on the --cluster-store option in Docker.
Workaround: A temporary solution involves pinning an older version of Docker. This workaround was used to unblock the CI (Continuous Integration).
Long-term Solution: The plan is to migrate to containerd with the CNI (Container Network Interface) network model.
Specific Changes in Zun:

Assignee: The issue has been assigned to "hongbin (hongbin034)."
Status Transition: The issue has moved from "New" to "Triaged."
Importance: The importance of the issue has been raised from "Undecided" to "High."
Additional Information:

There is a reference to a specific change made in Zun (https://review.opendev.org/c/openstack/zun/+/875203) where an older version of Docker was pinned to unblock the CI.
Long-term Solution:

The plan for a permanent solution involves migrating away from Docker to containerd, implementing the CNI network model.
In summary, it appears that the development team is actively working on addressing the issue by both implementing a temporary workaround and planning a more sustainable long-term solution by transitioning to containerd with the CNI network model. The issue has been triaged and marked as high importance. The assigned person is Hongbin, and there's a reference to a specific change that temporarily addressed the problem in the CI environment.