You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 27, 2023. It is now read-only.
Description
After upgrading to latest version of Docker Desktop for Mac 3.0.0, docker-compose up --build cmd throws the errors below that are preventing me from spinning up my containerized hobby project (a simple Python REST API). This error smells like a bug introduced by 3.0.0 because when I revert to 2.5.0.0 the issue goes away and I'm able to build my image and spin up my container without issue. The file/directory referenced in the error message does exist and has the following permissions: drwxr-xr-x. Any help resolving this issue would be great. If error is on my side, please let me know where I've strayed. Thanks!
ERROR: for <service_name> Cannot start service <service_name>: Mounts denied: approving path/to/project/root/dir: file does not exist
ERROR: Encountered errors while bringing up the project.
docker-compose up --build (executed in project root dir)
Describe the results you received:
The following error that prevents the container from being spun up.
Successfully built 34141e8d249d
Successfully tagged hotel_api_api:latest
hotel_api_postgres_1 is up-to-date
Recreating e98f9b0e1ab8_hotel_api_api_1 ... error
ERROR: for e98f9b0e1ab8_hotel_api_api_1 Cannot start service api: Mounts denied: approving path/to/project/root/dir: file does not exist
ERROR: for api Cannot start service api: Mounts denied: approving path/to/project/root/dir: file does not exist
ERROR: Encountered errors while bringing up the project.
Describe the results you expected:
Expected this command would launch my multi-container environment successfully (as it would for version before 3.0.0).
Output of docker version:
Client: Docker Engine - Community
Cloud integration: 1.0.4
Version: 20.10.0
API version: 1.41
Go version: go1.13.15
Git commit: 7287ab3
Built: Tue Dec 8 18:55:43 2020
OS/Arch: darwin/amd64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.0
API version: 1.41 (minimum version 1.12)
Go version: go1.13.15
Git commit: eeddea2
Built: Tue Dec 8 18:58:04 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v1.4.3
GitCommit: 269548fa27e0089a8b8278fc4fc781d7f65a939b
runc:
Version: 1.0.0-rc92
GitCommit: ff819c7e9184c13b7c2607fe6c30ae19403a7aff
docker-init:
Version: 0.19.0
GitCommit: de40ad0
Output of docker context show:
You can also run docker context inspect context-name to give us more details but don't forget to remove sensitive content.
The text was updated successfully, but these errors were encountered:
clpatterson
changed the title
Upgrading to Docker 3.0.0 Causing Mounts Denied: path/to/file: file does not exist Error
Upgrading to Mac Docker Desktop 3.0.0 Causing Mounts Denied: path/to/file: file does not exist Error
Dec 10, 2020
Description
After upgrading to latest version of Docker Desktop for Mac 3.0.0, docker-compose up --build cmd throws the errors below that are preventing me from spinning up my containerized hobby project (a simple Python REST API). This error smells like a bug introduced by 3.0.0 because when I revert to 2.5.0.0 the issue goes away and I'm able to build my image and spin up my container without issue. The file/directory referenced in the error message does exist and has the following permissions: drwxr-xr-x. Any help resolving this issue would be great. If error is on my side, please let me know where I've strayed. Thanks!
Steps to reproduce the issue:
Describe the results you received:
The following error that prevents the container from being spun up.
Describe the results you expected:
Expected this command would launch my multi-container environment successfully (as it would for version before 3.0.0).
Output of
docker version
:Output of
docker context show
:You can also run
docker context inspect context-name
to give us more details but don't forget to remove sensitive content.Output of
docker info
:The text was updated successfully, but these errors were encountered: