Prerequisites:
Before proceeding confirm the deployment is impacted by this issue by the following steps.
- Verify that the deployment is on vSphere Integrated Containers v0.8.0-7315-c8ac999 (Server Version), by running this command from a docker client:
docker -H 192.168.3.246:2376 --tls info
- Check if the ESXi host detects free space on the vSAN datastore by running this command:
Note: Connect to the shell of the ESXi host that attempted to run the container.
df -f
Verify the datastore had enough available space for the container's.
- Check if the Distributed Object Manager (DOM) is at maximum capacity by running this command:
cmmds-tool find -f json -t NODE_USAGE
Compare the maxComponents to the componentsReserved.
For example:
{
"uuid": "56f50b3f-ae91c1da-0285-ecf4bbebc1c0",
"owner": "56f50b3f-ae91c1da-0285-ecf4bbebc1c0",
"health": "Healthy",
"revision": "88",
"type": "NODE_USAGE",
"flag": "2",
"minHostVersion": "0",
"md5sum": "8ab85c882462568f73a5318a5de3b328",
"valueLen": "40",
"content": "{\"maxComponents\": 9000, \"dataComponents\": 5888, \"componentsReserved\": 9000, \"leafNum\": 1542, \"leafLimit\": 36000}",
"errorStr": "(null)"
}
This is a known issue affecting vSphere Integrated Containers.
Currently, there is no resolution.
To work around this issue, clean the vSAN objects. To clean vSAN obejects, file a support request support request with VMware Support and quote this Knowledge Base article ID (2149638) in the problem description. For more information, see
Filing a Support Request in Customer Connect (2006985).