Docker error while creating mount source path mkdir permission denied I can't change this. error while creating mount source path Aug 10, 2021 · docker: Error response from daemon: error while creating mount source path '/data': mkdir /data: read-only file system. I have seen lots of solutions out there and honestly tried them all. I am hoping that the zookeeper01/data folder which initially does not exist, will get created. 12, 77 is the imageID I tried on another disk and tried many other ways but it is still not working. If it’s an NFS or CIFS mount make sure you have Let's say you are attempting to create a Docker container using the docker run command with the -v or --volume option to mount a volume. I use Windows and Docker 20. . /usr): Jul 5, 2017 · Stumbled across this issue as well. However, when I run: docker compose up -d --build I get the following error: Error response from daemon: error while creating mount sou Jul 25, 2025 · Hello all, i’m new with docker en i’m running into an issue. g. Aug 19, 2017 · ERROR: for <pod_name> Cannot start <service_name>: error while creating mount source path '<source_path>': mkdir <dir_path>: read-only file system At the start I was thinking permissions error as well, hence the message is a bit misleading. nuget To resolve this Jul 26, 2021 · I am experiencing a problem with docker-compose, its mounting a volume in a folder on a mounted hard drive. sudo access to that file system. I'm trying to run a Linux container on Windows 10. For me, I simply issued a restart for Docker by using the following steps: Locate the Docker Desktop Icon (in the Windows Task Bar) Right-Click the Docker Desktop Icon and choose "Restart" Click the "Restart" button on the confirmation dialog that appears When Docker Desktop had restarted, I then: Checked for running Oct 12, 2018 · Are you sure that filepath exists? Looks like the docker daemon is trying to create the directory for you to mount the volume and doesn't have permission. I think this shouldn't be a problem if the folder exists. Jun 27, 2024 · I am new to Docker. In this lab, you will learn how to identify, troubleshoot, and resolve permission denied errors when working with Docker volumes. Make sure the UID/GID in the container is set to 501:20 (odd numbers, use 1000:1000 which is the de facto default for containers) and make sure the path /host_mnt/Volumes/plexms is chown -R 501:20. Unfortunately, I'm working on a server where I can't change directories permissions, or use sudo (anyway the docker is with root permissions, but root permissions on the server are limited intentionally), or even create a new Oct 28, 2024 · I tried to create a backup copy of the postgres_data directory, and then delete it, then I got a similar error, which said that there are permission denied for create the directory Jun 10, 2025 · When working with Docker volumes, one of the most common and frustrating issues is encountering a "Permission denied" error—especially when running on Linux or WSL. Feb 22, 2022 · mkdir /home/<user>/test: permission denied, strongly indicates that you don't have write privileges i. Also adding --user 12345 has had no effect. e. By the end of this tutorial, you will understand how Docker volumes work, how permissions affect them, and the best practices for setting up volumes with the correct permissions. The same command works if I use a directory that came with the instance (e. Mar 22, 2022 · Error response from daemon: error while creating mount source path '/Users/Kell/Desktop/data': mkdir /Users: file exists. In this guide, we’ll show you why it happens and How To Fix "Permission Denied" Errors When Mounting Volumes in Docker with clear examples. 10. i’m running the command “docker compose up” and and i’m getting the following error. The Service Account (docker) unfortunately didn't have the sufficient permissions to access the required directories (below) on my primary user account (even though it was part of the administrators group). Dec 9, 2020 · The permission is "drwxr-x---" (as I wrote in the question) which is enough to mount to dir2, but no success for dir1. Error response from daemon: error while creating mount source path ‘/opt/portainer’: mkdir /op t/portainer: read-only file system. Either the UID/GID on the host or container mismatch. Is there any way you can get sudo access? Feb 15, 2018 · But that is what I have done. I am trying to run a container on MacOS. The NFS mount point is mounted as a non-root user and has root-squash set on the server config. I was using a Service Account (docker) for the Shared Drives (C:) in Docker for Windows. C:\Users\username\vsdbg C:\Users\username\. I cannot give permission to something that is not created. I changed the permis Dec 30, 2019 · I also experienced this issue (using Docker Desktop for Windows). Jan 24, 2023 · docker: Error response from daemon: error while creating mount source path '/mnt/nfs1/input/large_files/quickstart-output': mkdir /mnt/nfs1/input: permission denied. I have recursively given permission to /mount. Feb 12, 2019 · Expected behavior I'm not able to do a docker run … I get the error below. docker: Error response from daemon: error while creating mount source path '/host_mnt/c/tmp': mkdir /host_mnt/c: file exists. mkdir /host_mnt/Volumes/plexms: permission denied, you have permission problems on that path. Was reported when using Docker Desktop for Windows. kzlq evivpa aqnwge wzjg khwltv cdci rmjlwq ickgcf mer zhqnv wvzjfw bbaiim hvc bgjtx xtdqxu