An incompatibility exists between the Docker version 29 (29.2.0+) running on the Docker host and the Docker version inside the High Availability (HA) container. The newer Docker version on the host is incompatible with the older versions inside the HA container, causing the controllers (Docker on the host and Docker inside the HA container) to fail when managing shared containers (e.g., so-core, so-mysql).
Use Case #1: Transitioning to Standalone (Non-HA) Environment
Follow this procedure to transition from a High Availability (HA)-managed environment to a standalone (non-HA) environment after stopping redundancy.
-
Ensure the Hot Standby Redundancy feature is fully stopped.
-
Access SSH port 22.
-
Execute the following command to remove all old containers:
docker container prune
- Access socli and execute the following command to start the Legacy Orchestrator services.
services start
Use Case #2: Transitioning to HA-Managed Environment
Follow this procedure to transition from a standalone (non-HA) environment to a HA-managed environment before starting redundancy.
Phase 1 – Remove All Old Containers on Both Sites
On site-A:
- Access socli and execute the following command to stop the services:
services stop
-
Access SSH port 22.
-
Execute the following command to remove all old containers:
docker container prune
On site-B:
- Access socli and execute the following command to stop the services:
services stop
-
Access SSH port 22.
-
Execute the following command to remove all old containers:
docker container prune
Phase 2 – Start Redundancy
-
Access socli on site-A.
-
Execute the following command to start redundancy:
redundancy control start
© 2026 Cisco and/or its affiliates. All rights reserved.
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms