Docker Community Forums

Share and learn in the Docker community.

Docker Desktop 2.2.0.0 - Mounts to CIFS Volumes are now failing on container start with error "host is down"

I’m hoping to get some help from the community on this recent problem I’ve encoutnered.

For a few years now, I’ve been running a few containers on Docker Desktop for Windows, some of which have volume mounts to CIFS shares on a NAS. Originally, I created persistent volumes for the CIFS shares using:

docker volume create --driver local --opt type=cifs --opt device=//<IP_Redacted>/sharedFiles/ --opt o="username=<Username_Redacted>,password=-<Password_Redacted>,file_mode=0777,dir_mode=0777" cifs-volume

I then, used this volume in my docker-compose.yml by defining it as an external volume:

version: "3.7"
services:
  someContainer:
    ...
    volumes:
      - cifs-volume:/sharedFiles
...
volumes:
  cifs-volume::
    external: true

I cannot stress engou, that this has worked fine for years now. However a few days ago, I began encountering this error on execution of docker-compose up -d:

ERROR: for someContainer Cannot start service someContainer: error while mounting volume ‘/var/lib/docker/volumes/cifs-volume/_data’: failed to mount local volume: mount //<IP_Redacted>/sharedFiles/:/var/lib/docker/volumes/cifs-volume/_data, data: username=<Username_Redacted>,password=<Password_Redacted>,file_mode=0777,dir_mode=0777: host is down

There are no recent changes to my NAS, my network, or my PC that can account for this recently occurring failure. My NAS remains completely reachable from my host Windows PC. My suspicion is that the precipitating event was a recent upgrade to Docke Desktop itslef. I’m now on version is 2.2.0.0 (42247).

I would appreciate any guidance that community can provide, that helps me get my CIFS volumes working again!

Hi dsbut,

I meet similar problems after upgrading Docker Desktop for Windows to 2.2 from 2.1. They decided to eliminate DockerNAT completely and it influenced on the networking to HOST machine from a container.

I found two alterations:

  1. It’s necessary to use host.docker.internal instead of 10.0.75.1 to access host machine
  2. If I use mount command from a container, cifs should use version 2.1, not 2.0