Don't automatically create a synchronized file share when the bind mount consistency is 'consistent' #12739
Description
Description
When...
- "Manage Synchronized file shares with Compose" is enabled in Docker Desktop under "Experimental features"
- A service has a bind mount with consistency set to "consistent" and it is the only bind mount referencing the source directory in the configuration
Current Behavior
A new synchronized share is created before the service starts, but according to the documentation the bind mount's consistency setting of "consistent" means the share will not be used.
Desired Behavior
A new synchronized share is not created, since according to the documentation the bind mount's consistency setting of "consistent" means the share will not be unused.
Additional Details
In the Synchronized File Sharing documentation there is a note that says:
When you create a new service, setting the bind mount option consistency to `:consistent` bypasses Synchronized file shares.
Which is followed by a tip that says:
Docker Compose can automatically create file shares for bind mounts. Ensure you're signed in to Docker with a paid subscription and have enabled both Access experimental features and Manage Synchronized file shares with Compose in Docker Desktop's settings.
And here is a screenshot of the current state of the documentation just in case:
These two details imply to me that the current behavior could be updated to simply skip creating the synchronized file share if it would otherwise go unused.