VIDB/VCFA 9.0.2 install fails with "failed to create task for container" error

Products

• VCF Operations
• VCF Automation

Issue/Introduction

After patching VCF Fleet Management from 9.0.0 → 9.0.2, and subsequently deploying VIDB/VCFA, the deployment fails while creating registry docker container:

LCMVSPHERECONFIG1000095 with an error that contains "Error response from daemon: failed to create task for container: failed to start shim: start failed:"

 

Fleet Management log path: /var/log/vrlcm/vmsp_bootstrap_####.log

docker: Error response from daemon: failed to create task for container: failed to start shim: start failed: dial unix {"version":3,"address":"unix:///run/containerd/s/...","protocol":"ttrpc"}: connect: invalid argument
ERR:INIT0002 - Initializing bootstrap machine

 

Fleet Management log path: /var/log/vrlcm/vmware_vrlcm.log

2026-03-02T23:24:21.840Z INFO ... Injecting task failure event. Error Code : 'LCMVSPHERECONFIG1000095'
java.lang.Exception: Failed to create services platform cluster. 

Environment

VCF Operations 9.0.2

Cause

The upgrade of VCF Fleet Management from 9.0.x.0 to 9.0.2.0 completes successfully but fails to restart the containerd service on the appliance.

Resolution

Restart containerd on the VCF Operations Fleet Management appliance.

Steps:

1. Connect to the Fleet Management instance via SSH as root.
   ssh root@<Fleet_ip>
   
   
2. Restart the containerd
   systemctl restart containerd
   
   
3. Ensure containerd is running
   systemctl status containerd
   
   
4. Retry failing step from the Fleet Management UI

 

Alternatively, if you found and applied the solution from KB - Error code: LCMVSPHERECONFIG1000095 at stage 6 while upgrading VCF Automation which basically just reboots the Fleet Management appliance, this effectively resolves the issue as well.