Docker error response from daemon mkdir

I’m facing the same problem right now.

Been trying latest Docker Desktop for Windows as well as the Docker Desktop from edge channel.

My setup details:

OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.18363 N/A Build 18363

> docker version
Client: Docker Engine - Community
 Version:           19.03.5
 API version:       1.40
 Go version:        go1.12.12
 Git commit:        633a0ea
 Built:             Wed Nov 13 07:22:37 2019
 OS/Arch:           windows/amd64
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          19.03.5
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.12
  Git commit:       633a0ea
  Built:            Wed Nov 13 07:29:19 2019
  OS/Arch:          linux/amd64
  Experimental:     true
 containerd:
  Version:          v1.2.10
  GitCommit:        b34a5c8af56e510852c35414db4c1f4fa6172339
 runc:
  Version:          1.0.0-rc8+dev
  GitCommit:        3e425f80a8c931f88e6d94a8c831b9d5aa481657
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

> docker-compose version
docker-compose version 1.25.1-rc1, build d92e9bee
docker-py version: 4.1.0
CPython version: 3.7.5
OpenSSL version: OpenSSL 1.1.1d  10 Sep 2019

When trying uncheck & check again shared drives in the Settings > Resources > File Sharing I’m being prompted to enter the user password all the time (I enter correct password). This happens only AFTER I face the mkdir /host_mnt/c: file exists error. When Docker is restarted I can (un)check shared drives successfully again, but as soon as the error comes by, it’s failing (continuously prompts for password).

#edit

After several tries, restarts and running docker-compose up I get a new error from SSHD:

ERROR: for nginx Cannot start service nginx: error while creating mount source path '/host_mnt/c/Users/samm/Desktop/wordpress-nginx-docker/logs/nginx': mkdir /host_mnt/c/Users/samm/Desktop/wordpress-nginx-docker/logs: transport endpoint is not connected

To reproduce, simply clone and docker-compose this repo.

Troubleshoot topics

Topics for all platforms

Make sure certificates are set up correctly

Docker Desktop ignores certificates listed under insecure registries, and does not send client certificates to them. Commands like docker run that attempt to pull from the registry produces error messages on the command line, like this:

As well as on the registry. For example:

Topics for Linux and Mac

Volume mounting requires file sharing for any project directories outside of $HOME

If you are using mounted volumes and get runtime errors indicating an application file is not found, access to a volume mount is denied, or a service cannot start, such as when using Docker Compose, you might need to enable file sharing.

Volume mounting requires shared drives for projects that live outside of the /home/ directory. From Settings, select Resources and then File sharing. Share the drive that contains the Dockerfile and volume.

Docker Desktop fails to start on MacOS or Linux platforms

On MacOS and Linux, Docker Desktop creates Unix domain sockets used for inter-process communication.

Docker fails to start if the absolute path length of any of these sockets exceeds the OS limitation which is 104 characters on MacOS and 108 characters on Linux. These sockets are created under the user’s home directory. If the user ID length is such that the absolute path of the socket exceeds the OS path length limitation, then Docker Desktop is unable to create the socket and fails to start. The workaround for this is to shorten the user ID which we recommend has a maximum length of 33 characters on MacOS and 55 characters on Linux.

Following are the examples of errors on MacOS which indicate that the startup failure was due to exceeding the above mentioned OS limitation:

Topics for Mac

Incompatible CPU detected

Docker Desktop requires a processor (CPU) that supports virtualization and, more specifically, the Apple Hypervisor framework. Docker Desktop is only compatible with Mac systems that have a CPU that supports the Hypervisor framework. Most Macs built in 2010 and later support it,as described in the Apple Hypervisor Framework documentation about supported hardware:

Generally, machines with an Intel VT-x feature set that includes Extended Page Tables (EPT) and Unrestricted Mode are supported.

To check if your Mac supports the Hypervisor framework, run the following command in a terminal window.

If your Mac supports the Hypervisor Framework, the command prints kern.hv_support: 1 .

If not, the command prints kern.hv_support: 0 .

See also, Hypervisor Framework Reference in the Apple documentation, and Docker Desktop Mac system requirements.

Topics for Windows

Volumes

Permissions errors on data directories for shared volumes

When sharing files from Windows, Docker Desktop sets permissions on shared volumes to a default value of 0777 ( read , write , execute permissions for user and for group ).

The default permissions on shared volumes are not configurable. If you are working with applications that require permissions different from the shared volume defaults at container runtime, you need to either use non-host-mounted volumes or find a way to make the applications work with the default file permissions.

Volume mounting requires shared folders for Linux containers

If you are using mounted volumes and get runtime errors indicating an application file is not found, access is denied to a volume mount, or a service cannot start, such as when using Docker Compose, you might need to enable shared folders.

With the Hyper-V backend, mounting files from Windows requires shared folders for Linux containers. From Settings, select Shared Folders and share the folder that contains the Dockerfile and volume.

Support for symlinks

Symlinks work within and across containers. To learn more, see How do symlinks work on Windows?.

Avoid unexpected syntax errors, use Unix style line endings for files in containers

Any file destined to run inside a container must use Unix style n line endings. This includes files referenced at the command line for builds and in RUN commands in Docker files.

Docker containers and docker build run in a Unix environment, so files in containers must use Unix style line endings: n , not Windows style: rn . Keep this in mind when authoring files such as shell scripts using Windows tools, where the default is likely to be Windows style line endings. These commands ultimately get passed to Unix commands inside a Unix based container (for example, a shell script passed to /bin/sh ). If Windows style line endings are used, docker run fails with syntax errors.

For an example of this issue and the resolution, see this issue on GitHub: Docker RUN fails to execute shell script.

Path conversion on Windows

On Linux, the system takes care of mounting a path to another path. For example, when you run the following command on Linux:

It adds a /work directory to the target container to mirror the specified path.

However, on Windows, you must update the source path. For example, if you are using the legacy Windows shell ( cmd.exe ), you can use the following command:

This starts the container and ensures the volume becomes usable. This is possible because Docker Desktop detects the Windows-style path and provides the appropriate conversion to mount the directory.

Docker Desktop also allows you to use Unix-style path to the appropriate format. For example:

Working with Git Bash

Git Bash (or MSYS) provides a Unix-like environment on Windows. These tools apply their own preprocessing on the command line. For example, if you run the following command in Git Bash, it gives an error:

This is because the character has a special meaning in Git Bash. If you are using Git Bash, you must neutralize it using \ :

Also, in scripts, the pwd command is used to avoid hardcoding file system locations. Its output is a Unix-style path.

Combined with the $() syntax, the command below works on Linux, however, it fails on Git Bash.

You can work around this issue by using an extra /

Portability of the scripts is not affected as Linux treats multiple / as a single entry. Each occurence of paths on a single line must be neutralized.

In this example, The $(pwd) is not converted because of the preceding ‘/’. However, the second ‘/work’ is transformed by the POSIX layer before passing it to Docker Desktop. You can also work around this issue by using an extra / .

To verify whether the errors are generated from your script, or from another source, you can use an environment variable. For example:

It only expects the environment variable here. The value doesn’t matter.

In some cases, MSYS also transforms colons to semicolon. Similar conversions can also occur when using

because the POSIX layer translates it to a DOS path. MSYS_NO_PATHCONV also works in this case.

Virtualization

Your machine must have the following features for Docker Desktop to function correctly.

WSL 2 and Windows Home

1. Virtual Machine Platform
2. Windows Subsystem for Linux
3. Virtualization enabled in the BIOS
4. Hypervisor enabled at Windows startup

Hyper-V

On Windows 10 Pro or Enterprise, you can also use Hyper-V with the following features enabled:

Docker Desktop requires Hyper-V as well as the Hyper-V Module for Windows Powershell to be installed and enabled. The Docker Desktop installer enables it for you.

Docker Desktop also needs two CPU hardware features to use Hyper-V: Virtualization and Second Level Address Translation (SLAT), which is also called Rapid Virtualization Indexing (RVI). On some systems, Virtualization must be enabled in the BIOS. The steps required are vendor-specific, but typically the BIOS option is called Virtualization Technology (VTx) or something similar. Run the command systeminfo to check all required Hyper-V features. See Pre-requisites for Hyper-V on Windows 10 for more details.

To install Hyper-V manually, see Install Hyper-V on Windows 10. A reboot is required after installation. If you install Hyper-V without rebooting, Docker Desktop does not work correctly.

From the start menu, type Turn Windows features on or off and press enter. In the subsequent screen, verify that Hyper-V is enabled.

Virtualization must be enabled

In addition to Hyper-V or WSL 2, virtualization must be enabled. Check the Performance tab on the Task Manager:

If you manually uninstall Hyper-V, WSL 2 or disable virtualization, Docker Desktop cannot start. See Unable to run Docker for Windows on Windows 10 Enterprise.

Hypervisor enabled at Windows startup

If you have completed the steps described above and are still experiencing Docker Desktop startup issues, this could be because the Hypervisor is installed, but not launched during Windows startup. Some tools (such as older versions of Virtual Box) and video game installers disable hypervisor on boot. To reenable it:

1. Open an administrative console prompt.
2. Run bcdedit /set hypervisorlaunchtype auto .
3. Restart Windows.

You can also refer to the Microsoft TechNet article on Code flow guard (CFG) settings.

Windows containers and Windows Server

Docker Desktop is not supported on Windows Server. If you have questions about how to run Windows containers on Windows 10, see Switch between Windows and Linux containers.

You can install a native Windows binary which allows you to develop and run Windows containers without Docker Desktop. However, if you install Docker this way, you cannot develop or run Linux containers. If you try to run a Linux container on the native Docker daemon, an error occurs:

Networking issues

IPv6 is not (yet) supported on Docker Desktop.

Источник

Error response from daemon: error while creating mount source path, mkdir /run/desktop/mnt/host/c/Users/. file exists #12403

Actual behavior

When I want to run the image with this command:

I get this error message:

Expected behavior

The container should be started and the mount point should appear in /var/www/ .

Information

• Windows Version: Microsoft Windows [Version 10.0.19043.1348]
• Docker Desktop Version: Docker Desktop 4.2.0 (70708)
• WSL2 or Hyper-V backend? WSL2
• Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No.

Steps to reproduce the behavior

1. I have two physical drives, C: and E:
2. On E: , each user has their own working directories, like E: . This is because I don’t like spaces in the user name Windows creates for me.
3. There is a file E: Projektek

src2my-file.html .
I created a junction in CMD.EXE, run as Administrator: mklink /J «c:Users src6» e: Projektek

src2 . Note: has no spaces in it, while is my first name and my last name, separated by a space.

stops with an error message:

Why is it an error that src6 exists? Of course, it does, I want to see its content under /var/www/.

This problem seems to be similar to #5516 but the solution written there does not solve the problem for me.

The text was updated successfully, but these errors were encountered:

Источник

Error when mounting host path with Docker for Windows — «Permission Denied» #3385

Expected behavior

I’m not able to do a docker run … I get the error below. I’m trying to run a Linux container on Windows 10.
error while creating mount source path ‘/host_mnt/c/Users/xyz/AppData/Roaming/Microsoft/UserSecrets’: mkdir /host_mnt/c/Users/xyz/AppData: permission denied.

Actual behavior

Run the container successfully

Information

• Windows Version: Windows 10
• Docker for Windows Version: 2.0.0.0-win78 (28905)
  I checked the Drive sharing config and Drive sharing is enabled with credentials that have local admin rights on my machine.

Steps to reproduce the behavior

The text was updated successfully, but these errors were encountered:

Same problem here.

Same here.
For context, I have an Azure Active Directory account and I had to create another local one with the same name to be able to use Docker AT ALL. But it seems to still be unable to mount folders inside the user directories.

Also have this problem. Creates volumes fine once you add the local account, the container just cant access them. Doesn’t seem matter what rights I put on the .docker folder either for the new account user.

Also see «Error response from daemon: error while creating mount source path ‘/host_mnt/c/Users//.docker/Volumes/elasticdata-elasticsearch-0/pvc-64d22745-7883-11e9-9d67-00155d021b09’: mkdir /host_mnt/c/Users//.docker: permission denied» when inspecting the pod. File exists in the user directory and no issue with volumes themselves it seems.

Tried unsuccessfully to find a way to change the directory for these volumes to somewhere I would have more control as having them on another drive would be useful also.

The solution seems to be to add the Users group to the .docker folder and grant full access. Just the new local account access wasn’t enough for me.

@DarrenV79 could you please explain in more details how to add Users group to .docker folder and grant full access? thanks in advance

@daton89 To add a group to a directory you in windows follow these steps:

1. Right-click the dir
2. Click properties
3. click the security tab
4. click the «Edit» button.
5. click the add button
6. Type «users» in the text box
7. click «Check Names» (should auto fill/update for you)
8. click okay
9. Highlight your newly added group.
   10 . Under «Permissions for [User/Groupname]» select Full control
10. click apply
11. Click «OK»
12. Click «OK»

With all that out of the way I will report that adding the «Users» group to just the .docker file in my c:Users[home].docker dir did not work.

What did work was having the Users group added to at least the .docker, the great great great grandparent dir of my working dir, and the local dir I was trying to mount to my container.

Same problem. Trying to give access to users.

@freerider7777 were you able to resolve your issue?

@alexkoepke Yes, I gave permissions from @DarrenV79’s workaround and it worked

What did work was having the Users group added to at least the .docker, the great great great grandparent dir of my working dir, and the local dir I was trying to mount to my container.

@alexkoepke this solved it for me as well

@DarrenV79 ‘s answer solved my issue as well.

Giving full permissions only to the .docker folder didn’t seem to work for me. Giving full permissions to the entire User folder seemed to do the trick, even though it is nasty.

My setup is as follows:

• I have a primary account called «User» onto which I’m currently logged in and do my development work
• I have a user called «DockerDiskSharing» with full admin rights, which I intend to use for Docker to run with

The steps I took were:

1. I opened a command prompt with admin rights and added the DockerDiskSharing user to the docker-users group by running

net localgroups docker-users DockerDiskSharing /add

1. I went to Docker -> Settings -> Shared Drives, I clicked «Reset credentials» and added the DockerDiskSharing user’s credentials. I ticked C drive (my main partition) and the D drive (where my project is located)
2. I opened a command prompt with admin rights and gave full access permissions to the entire Users/User folder by running:

icacls «C:UsersUser» /q /c /t /grant docker-users:F

Still unsure which folders in particular it needs permissions to read/write to though from Users/User but it worked.

Источник

phenomenon

Stop the container (for MySQL) that sets volumes → Start it

$ docker-compose up -d
Creating volume "sample_db-store" with default driver
Creating hoge_db_1 ... error

ERROR: for sample_db_1  Cannot start service db: error while creating mount source path '/host_mnt/Users/~/docker/mysql/sql': mkdir /host_mnt/Users/~/docker/mysql/sql: file exists
ERROR: Encountered errors while bringing up the project.

An error message stating «The host directory cannot be mounted» is displayed and the container cannot be started.

Operating environment

Solutions

If you are using Docker Desktop for Windows

Docker Desktop for Windows → [Settings] → [Shared Drives] → [Reset Credentials] → Reauthentication (check the corresponding path)

[reference]
https://www.nuits.jp/entry/docker-for-windows-mkdir-file-exists

If you are using Docker Desktop for Mac

Docker Desktop for Mac → [preferences…] →[Resources] →[File Sharing]

After deleting ** / Users **, [apply & Restart]

Then add ** / Users ** and [apply & Restart]

What I tried before solving

Operating background

With docker-compose, I was building a MySQL container as follows.

docker-compose.yml

version: '3'
services:
  db:
    image: mysql:8.0
    volumes:
      - db-store:/var/lib/mysql
      - ./logs:/var/log/mysql
      - ./docker/mysql/my.cnf:/etc/mysql/conf.d/my.cnf
      - ./docker/mysql/sql:/docker-entrypoint-initdb.d
    environment:
      - MYSQL_DATABASE=${DB_NAME}
      - MYSQL_USER=${DB_USER}
      - MYSQL_PASSWORD=${DB_PASS}
      - MYSQL_ROOT_PASSWORD=${DB_PASS}
      - TZ=${TZ}
    ports:
      - ${DB_PORT}:3306
volumes: db-store

In volumes, in addition to those related to data and log

docker-compose.yml

 - ./docker/mysql/sql:/docker-entrypoint-initdb.d

Is defined.

In the image for MySQL, when mounting to /docker-entrypoint-initdb.d, the .sql, .sh file existing in the specified host side directory is read and executed when the container is started for the first time. ..
https://hub.docker.com/_/mysql/

Therefore, the SQL for table creation and the shell script for executing SQL were placed in the directory ./docker/mysql/sql on the host side to be mounted on the container. It works without any problem at the first startup. The SQL and shell script I put in between were running without any problems.

However, once the container was stopped with docker-compose stop, this phenomenon occurred at startup with docker-compose up.

Tried (1): Delete volume

I found information that a similar behavior could be solved by deleting the volume, so I tried deleting the container and the named volume.

$ docker-compose down --volumes

Removing sample_db_1    ... done
Removing volume sample_db-store

$ docker-compose up -d

Failure.

Tried (2): Update the authentication information of the shared folder of Docker Desktop for Mac (this solution)

Similar Docker Daemon error

docker: Error response from daemon: error while creating mount source path '/host_mnt/c/tmp': mkdir /host_mnt/c: file exists.

Was reported when using Docker Desktop for Windows.
However, I couldn’t find any reports of similar errors in Docker Desktop for Mac.

It’s no good, but the flow is a little different from Windows, but when I tried to imitate the solution of the above error with Docker Desktop for Mac, it worked.

Cause

I’m wondering if something went wrong with the Docker Desktop Volumes sharing settings and I couldn’t access the directory information on the host side, but I don’t know the details.

If you know the root cause, please let me know: qiitan-cry:

This post illustrates how you can mount a GCS bucket using GCSFuse on your host machine and expose it as a volume to a Docker container.

PROBLEM

You want to volume mount a FUSE-mounted directory to a container, for example:

When attempting to run the container…

docker run -it --rm -v /my-kfc-bucket:/home busybox

… an error occurred:

docker: Error response from daemon: error while creating
mount source path '/my-kfc-bucket': mkdir /my-kfc-bucket: 
file exists.

SOLUTION

Unmount the existing FUSE-mounted directory.

sudo umount /my-kfc-bucket

Mount it back with the following option. Because this command with -o allow_other must be executed with sudo privilege, you will need to change the root ownership to yourself (via –uid and –gid) so that you can easily read/write within the directory.

sudo gcsfuse 
  -o allow_other 
  --uid $(id -u) 
  --gid $(id -g) 
  gcs-bucket /my-kfc-bucket  

If it is successful, the output should look like this:

Start gcsfuse/0.40.0 (Go version go1.17.6) for app "" using mount point: /my-kfc-bucket
Opening GCS connection...
Mounting file system "gcs-bucket"...
File system has been successfully mounted.

Rerun the docker container.

docker run -it --rm -v /my-kfc-bucket:/home busybox

Now, you can read/write the GCS bucket’s data from the container. In this example, the GCS bucket’s data is located in /home.