Config file '/docs/mkdocs.yml' does not exist.

[bashirs-investing]

Description

i pull the latest squidfunk/mkdocs-material image to use on my docker
docker pull squidfunk/mkdocs-material

and when i run the docker :
C:\Users\bashirs\GIT> docker run --rm -it -p 8000:8000 -v C:\Users\bashirs\GIT\Docs:/docs squidfunk/mkdocs-material

i get this error :

INFO - Building documentation...
Config file '/docs/mkdocs.yml' does not exist.

Expected behavior

it worked before pulling the latest version

System information

i'm running docker desktop Version 2.0.0.3 on Windows 10

[squidfunk]

I just tried the latest Docker image on OS X and it works. I have no way to test it on Windows. Please provide your mkdocs.yml and all other data listed in the issue template or we might not be able to help you.

Also, is your mkdocs.yml located in C:\Users\bashirs\GIT\Docs?

[bashirs-investing]

for your question the answer is yes
the mkdocs.yml located in C:\Users\bashirs\GIT\Docs

and this is the content of the mkdocs.yml :

site_name: 'Investing.com Technologies Docs'
site_author: 'Bs'

theme:
name: 'material'
language: 'en'
palette:
primary: 'indigo'
accent: 'indigo'
font:
text: 'Roboto'
code: 'Roboto Mono'

[squidfunk]

Configuration looks fine to me (assuming the indentation is correct). Did you upgrade Docker lately? 2.0.x looks like a new major release, which may explain the sudden breakage.

Somebody else experiencing issues with Docker on Windows?

[bashirs-investing]

yes i did upgrade the docker .
but as much as i remember i did run the old mkdocs image on the new docker version and it worked

[squidfunk]

Could you please verify this again? Just take an older version, for example 4.1.1 or 4.0.0, and try to run it. If it also does not run, it's definitely related to the new Docker version.

[squidfunk]

Closing for housekeeping.

[UlricGenievre]

I had same issue.
Reset credentials of Docker for Windows solved it.
As usual ¯_(ツ)_/¯

[FabRons]

Same issue on CentOS, update docker solved it.

docker version
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Version: 1.0.5

Remove old version:
dnf remove docker

Install docker-ce:
dnf config-manager --add-repo=https://download.docker.com/linux/centos/docker-ce.repo
dnf install containerd.io --nobest docker-ce

Enable docker:
systemctl enable --now docker

Check version:
Client: Docker Engine - Community
Version: 19.03.4
API version: 1.39 (downgraded from 1.40)
Go version: go1.12.10

Server: Docker Engine - Community
Engine:
Version: 18.09.1
API version: 1.39 (minimum version 1.12)
Go version: go1.10.6

Open ports:
firewall-cmd --permanent --add-port 8000/tcp

Restart firewall:
systemctl restart firewalld

Launch mkdocs-material again

[opus131]

Just in case anyone else finds this GH issue after encountering the same problem:

It is not related to mkdocs-material, but rather to the issue described here: docker-archive/toolbox#673

TLDR:

A possible solution (or rather workaround) is to prepend the command with MSYS_NO_PATHCONV=1, so that the full command is
MSYS_NO_PATHCONV=1 docker run --rm -it -p 8000:8000 -v ${PWD}:/docs squidfunk/mkdocs-material

To avoid having to prepend every time, you can add MSYS_NO_PATHCONV=1 to your .bashrc. If that feels to heavy-handed, or causes problems in other places, you can scope it to the docker command by doing smth like this (also in your .bashrc):

docker()
{
  MSYS_NO_PATHCONV=1
  "docker.exe" "$@"
  MSYS_NO_PATHCONV=0
}