In most cases, you should use one of the recommended methods that don't require manual configuration. A workaround is to bind to a specific IP address e.g. This is an artifact of the new amework in Big Sur. Therefore you cannot bind to port 53 on all interfaces with a command like docker run -p 53:53.
Use this method only for special cases and custom configurations. TCP and UDP port 53 (DNS) are bound on the host when Docker Desktop starts. TCP socket: This method should work for any Docker version and operating system. The file or directory is referenced by its absolute path on the host machine. When you use a bind mount, a file or directory on the host machine is mounted into a container. Bind mounts have limited functionality compared to volumes. If the Connection successful message doesn't appear, check your Docker Machine executable setting on the Docker | Tools page. Bind mounts have been around since the early days of Docker. If you get permission denied errors, add the current user to the docker group on the machine, log out, and then log back in.ĭocker Machine: If you are using Docker Toolbox for Windows or macOS, this is the recommended option for connecting to the Docker API. Unix socket: This is the recommended connection option for Linux. Select the method for connecting to the Docker API.ĭocker for Windows: The recommended option when using Docker Desktop for Windows.ĭocker for Mac: The recommended option when using Docker Desktop for Mac.
