Closed james-nesbitt closed 7 years ago
This sometimes occurs when a project has been "down"ed, but volumes were not removed.
It is unclear how it is that docker thinks that the driver has changed, but the issue can be mitigated by removing volumes when you down a project:
-> % radi down --compose.removevolumes
this will not be handled in this project.
When I run the local up orchestration command, I get an error regarding existing volumes: