full_stack_example - windows - Cannot create container for service metricbeat - invalid bind mount spec "/hostfs:ro"

[michael-wolfenden]

When following the instructions outlined in A Full Stack in One Command and running

docker-compose -f .\docker-compose-windows.yml up

I get the following error:

Creating network "fullstackexample_stack" with the default driver
Creating nginx ...
Creating elasticsearch ...
Creating mqsql ...
Creating apache2 ...
Creating nginx
Creating apache2
Creating mqsql
Creating elasticsearch ... done
Creating kibana ...
Creating kibana ... done
Creating configure_stack ...
Creating configure_stack ... done
Creating heartbeat ...
Creating heartbeat
Creating metricbeat ...
Creating packetbeat ...
Creating metricbeat
Creating filebeat ...
Creating packetbeat
Creating metricbeat ... error

ERROR: for metricbeat  Cannot create container for service metricbeat: invalid bind mount spec "/hostfs:ro": invalid volCreating filebeat ... done

I have the following versions installed

docker compose

> docker-compose version
docker-compose version 1.14.0, build c7bdf9e3
docker-py version: 2.3.0
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.0.2j  26 Sep 2016

docker

> docker version
Client:
 Version:      17.06.1-ce
 API version:  1.30
 Go version:   go1.8.3
 Git commit:   874a737
 Built:        Thu Aug 17 22:48:20 2017
 OS/Arch:      windows/amd64

Server:
 Version:      17.06.1-ce
 API version:  1.30 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   874a737
 Built:        Thu Aug 17 22:54:55 2017
 OS/Arch:      linux/amd64
 Experimental: true

docker for windows

Docker - Community Edition
Version 17.06.1-ce-win24 (13025)
Channel: stable
54dc09c

windows

> [System.Environment]::OSVersion.Version

Major  Minor  Build  Revision
-----  -----  -----  --------
10     0      15063  0

miscellaneous information

• I have both C and D as shared drives in docker for windows and am running docker-compose from D:\Dev\full_stack_example
• I also extracted the folder to C:\Users with the same result
• Removing metricbeat from the compose file worked insofar as the other containers started and I could log into kibana however a number of dashboard failed due to the missing metricbeat index

[gingerwizard]

You can comment out this line

https://github.com/elastic/examples/blob/master/Miscellaneous/docker/full_stack_example/docker-compose-windows.yml#L187

as a workaround - this will give you Metricbeat stats other than FS usage. This shouldn't, however, be required. We are attempting to mount the root of the hyperV VM FS. I'll try to recreate with your env specifics thanks.