-
Notifications
You must be signed in to change notification settings - Fork 95
Docker 1.13 support/interop #882
Comments
Can the volume can be re-formatted to destroy the data in the volume. |
Summary: Single replica works fine. Since VMDK volume can only be used by one docker host at any time, replicas > 1 will fail to start.
CLI is backward compatible and no additional work required.
VMDK volume with labels do not shown up in list though inspect shows label
Labels are stored in local metadata.db and are not available on another host. Docker doesn't correctly handle labels for shared volumes. So, we can safely ignore this for now.
Flocker bug couldn't be reproduced with VMDK driver. We are good. There is a weird docker behavior though. If volume is in use by another VM, we correctly fail the request but
|
Follow-up actions:
|
Plugin support (Ship guest docker volume plugin as managed plugin #886)
docker new commands
docker introduce "docker stack deploy" from a compose file, need to test this new command with docker-volume-vsphere plugin (PR27998)
docker changes to existing commands
Remove --name from docker volume create (PR23830), need test to verify plugin works for both old and new format
Add support for filtering volumes by label (PR25628), docker-volume-vsphere plugin need to support "docker volume ls --filter label".
Add a --force flag in docker volume rm to forcefully purge the data
of the volume that has already been deleted (PR23436). With suppport multiple-ESX host which shared same storage, we may see similar issue as flocker, need to verify "volume rm -f" can solve this issue
The text was updated successfully, but these errors were encountered: