Ah, right, I know why it happens. There's a race condition in the local provider's destruction code.
When destroying the environment, the agent is signalled, which instructs it to tear itself down and remove its service files. After signalling, the client code will also attempt to stop and remove the service. If the service is already gone, then this error is displayed.
I'll see if I can neaten it up, but I reiterate that it has nothing to do with storage or the configuration you specified.
Ah, right, I know why it happens. There's a race condition in the local provider's destruction code.
When destroying the environment, the agent is signalled, which instructs it to tear itself down and remove its service files. After signalling, the client code will also attempt to stop and remove the service. If the service is already gone, then this error is displayed.
I'll see if I can neaten it up, but I reiterate that it has nothing to do with storage or the configuration you specified.