Creation of the volume worked fine and it was placed in the correct fabric network after the initial
docker-compose up -d
But upon the second try, docker-compose up -d gave this error message:
ERROR: Configuration for volume testvol specifies "network" driver_opt vol-test-fabric, but a volume with the same name uses a different "network" driver_opt (None). If you wish to use the new configuration, please remove the existing volume "testvol" first:
$ docker volume rm testvol
When provisioning a volume in a custom fabric network the
tritonnfs
driverOptions
shownull
instead of the configured network.PI:
20200103T034110Z
sdc-docker image:docker release-20200102-20200103T002424Z-g3faf7f9
sdc-volapi image:volapi release-20200102-20200103T005353Z-g5210f51
Steps to reproduce (with the triton docker API):
vol-test-fabric
in this example, then run the following:The output should look like this:
Came across this when using
docker-compose
with adocker-compose.yml
like this:Creation of the volume worked fine and it was placed in the correct fabric network after the initial
But upon the second try,
docker-compose up -d
gave this error message: