Unable to provision a container in VIC error: No volume store named (default) exists

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:
When you create or run a container, the Docker operation fails with an error about a missing volume store.

Running/provisioning the container fails with error:

docker: Error response from daemon: No volume store named (default) exists.

or in the docker-personality.log:

ERROR Handler for POST /v1.24/containers/create returned error: No volume store named (default) exists

Environment

VMware vSphere Integrated Containers 1.x

Cause

By default, vic-machine create does not create a volume store when the vSphere administrator deploys a VCH. To run containers from images that use volumes, the vSphere administrator must specify a volume store named default when they deploy the VCH.

Resolution

Deploy a VCH by using the vic-machine create --volume-store option to create a VCH with a volume store named :default. See --volume-store in VCH Deployment Options and Specify Volume Stores in Advanced Examples of Deploying a VCH in vSphere Integrated Containers Installation. Use docker volume inspect to get information about the volume.

vic-machine-operating_system create
--target '[email protected]':password@vcenter_server_address/dc1
--compute-resource cluster1
--bridge-network vch1-bridge
--image-store 'datastore 1'
--volume-store 'datastore 1'/volumes:default
--name vch1
--no-tls