All my containers are no longer bind mounting. Is there a change in the formatting of the bind command I need to make?
I have about 20 containers that were all working before the update was installed. Some are throwing an error and not starting. others are starting but not mounting the correct data, ie they look like a fresh container. As a relatively new docker user, I am not sure where to start troubling shooting. I have found discussions about file cache/consistency commands but that seems to be related to a different problem. Windows 10 is fully updated.
Alternatively, what is the best way to downgrade docker desktop back to 2.1?
It would appear that Docker 2.3.0.2 has issues with bind mounts on windows, I, and others, downgraded to 2.2.0.5 to resolve the issue. I found a workaround here: https://github.com/microsoft/mssql-docker/issues/600
I have found some issues with 2.3.0.3 as well, that are not present on 2.2.0.5: It will fail to create a file on a bind mount when doing so as a non root user. Specifically when i try to restore an sqlserver-2019-based database from backup using a bind mount for the data directory, it will fail when restoring to a clean database and the database file (i.e databasename.mdf) is not present. The database process is unable to create the file on the bind mount.
This might be a breaking change, but correct behavior or a bug in docker, I dont really care at the moment. For now, I have reverted back to 2.2.0.5 again.
