--cluster-store does not work with Docker 23

[Michal Nasiadka]

Docker 23.0 is out and it does not support --cluster-store.
What is the required configuration to get Zun working with Docker 23?

[hongbin (hongbin034)]

Zun uses kuryr-libnetwork, which relies on the --cluster-store option. There is no obvious workaround without this option.

The mitigation is to pin an older version of docker (like what we did to unblock the CI: https://review.opendev.org/c/openstack/zun/+/875203

The long-term solution is to migrate to containerd with CNI network model.

[Jan Gutter (jangutter)]

Unfortunately the mitigation isn't working for Debian Bookworm, which means kolla-ansible will have to drop Zun support for Bookworm until this issue is resolved.

https://review.opendev.org/c/openstack/kolla-ansible/+/894573

[hongbin (hongbin034)]

ACK. The goal is to fix it in "C" release.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/zun/+/903884
Committed: https://opendev.org/openstack/zun/commit/19f6d7854de9a0b5e65ee97e21122c171ab66f64
Submitter: "Zuul (22348)"
Branch: master

commit 19f6d7854de9a0b5e65ee97e21122c171ab66f64
Author: Hongbin Lu <email address hidden>
Date: Mon Dec 18 12:39:34 2023 +0000

    Switch to "local" mode for kuryr libnetwork scope

    Docker has removed external cluster store in latest version.
    Therefore, we switch to "local" mode to work around.

    Closes-Bug: #2007142
    Change-Id: I31d140a75dae2ddd23551e648d0492327a8d8c8e

[harrysalt (harrysalt)]

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.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/zun 13.0.0.0rc1 release candidate.