VOLUME instruction causes trouble

[joostmeijles]

I am using Windows 10 update 1809 and Docker Desktop for Windows 2.0.0.3.

I start the system using a docker-compose file that overlays a bind-mount at the data directory location;

version: '2.4'

services:
 mssql:
  image: ...
  isolation: process
  environment:
    ACCEPT_EULA: "Y"
    sa_password: ${SQL_SA_PASSWORD}
  volumes:
    - .\data\mssql:C:\Data

With above setup I had following error:

• ssql_1 | Invoke-Sqlcmd : Cannot detach the database error when SQL server somehow was not properly shutdown (not killed)

This problem seem to be related to the VOLUME instruction in the Dockerfile (e.g.

sitecore-images/images/9.0.2 rev. 180604/windowsservercore-ltsc2019/sitecore-sqldev/Dockerfile

Line 39 in 5f35d9d

VOLUME ${DATA_PATH}

)

When I remove the VOLUME instruction these problems (see avivasolutionsnl/sitecore-docker#49) do no longer occur.

As there is no real added value for the VOLUME instruction in the Dockerfile, e.g. volume usage can be specified in the docker-compose file, I removed the instruction for the avivasolutionsnl/sitecore-docker repo.

[pbering]

Hi there! The reason for the VOLUME in solr and sql images, was at some point to ensure data was persisted even without mounting a volume, also know as "anonymous volumes". But I would like to get rid of that to avoid polluting machines with those volumes when not using explicit volumes (mostly used for demoing and quick prototyping).

I will remove the VOLUME from solr and sql xm/xp 1803 and ltsc2019.

Thanks for helping 👍

[pbering]

Closed with 09030cb