Can somebody please update on this issue. regards  Thamanna Farhath From: Thamanna Farhath <thamanna.f@zybisys.com> To: "openstack-discuss"<openstack-discuss@lists.openstack.org> Date: Wed, 15 Apr 2026 09:41:50 +0530 Subject: [zun][kolla] Zun Deployment with Docker Version Constraints in Kolla-Ansible 2023.1 Hi openstack community, I am working on deploying Zun using Kolla-Ansible (OpenStack 2023.1 – Antelope) and came across a known limitation in the documentation: Kuryr does not support Docker 23+ due to the removal of the --cluster-store option. Suggested workaround is to pin Docker to version 20.x using: docker_apt_package_pin: "5:20." docker_yum_package_pin: "20." My current setup: Existing cluster running Docker 29.x (no Zun) I want to avoid downgrading Docker on existing nodes Clarifications needed: Can we run mixed Docker versions (existing compute nodes on 29.x, new compute nodes with Zun on 20.x)? Is it safe/recommended to use dedicated compute nodes only for Zun with Docker 20.x? Is this issue still open, or are there alternatives? Looking for best practices to enable Zun without impacting the current cluster Thanks & regards, Thamanna Farhath Disclaimer :  The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender.   E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email." Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."