Docker for M1 update released! Docker Desktop preview 3.1.0 (60984)

by

[https://docs.docker.com/docker-for-mac/apple-m1/](https://docs.docker.com/docker-for-mac/apple-m1/)

## Fixes since the Apple Silicon preview 7

**Docker Desktop preview 3.1.0 (60984)**

2021-02-11

* Kubernetes now works (although you might need to reset the cluster in our Troubleshoot menu one time to regenerate the certificates).
* osxfs file sharing works.
* The host.docker.internal
and vm.docker.internal
DNS entries now resolve.
* Removed hard-coded IP addresses: Docker Desktop now dynamically discovers the IP allocated by macOS.
* The updated version includes a change that should improve disk performance.
* The **Restart** option in the Docker menu works.

6 thoughts on “Docker for M1 update released! Docker Desktop preview 3.1.0 (60984)”

  1. Even though this version of Docker Desktop is still considered a “preview”, I couldn’t help but notice the new download URL includes the word “stable”. They appear to be preparing for a more regular release cycle!

    For comparison, here are the **CURRENT download URLs** for Mac M1 vs Mac Intel:

    \>> desktop.docker.com/mac/stable/arm64/60984/Docker.dmg
    \>> desktop.docker.com/mac/stable/Docker.dmg

    Here is the **OLD download URL** for the M1 preview 7:
    \>> desktop.docker.com/mac/m1preview/Docker-AppleSilicon-Preview7.dmg

    Reply

  3. The release notes do not specifically mention dnsmasq, but I am hoping the “hard-coded IP” change fixes the various Docker + dnsmasq issues that I and many others have run into.

    >Removed hard-coded IP addresses: Docker Desktop now dynamically discovers the IP allocated by macOS.

    Here are a few related conversations

    * laravel/valet [Valet breaks Docker on M1](https://github.com/laravel/valet/issues/1031)
    * tighten/takeout [Connection refused trying to connect to registry-1.docker.io](https://github.com/tighten/takeout/issues/209)
    * docker/for-mac [Unable to pull from registry-1.docker.io](https://github.com/docker/for-mac/issues/5186)
    * docker forums [Error response from daemon: Get https://registry-1.docker.io/v2/%5D(https://forums.docker.com/t/error-response-from-daemon-get-https-registry-1-docker-io-v2/23741)

    In my case, the Docker container IPs appear to have changed from 192.168.64.x (which was conflicting with dnsmasq?) to a completely different IP range of 172.19.0.x. I haven’t been able to reproduce the issue after the upgrade!

    Reply

  5. I’m only a little bitter that my website build times are 30% faster than my i9 Desktop in WSL2. So far I haven’t noticed anything that doesn’t work but I mostly use docker for web development.

    Reply

  6. At this time I’m trying to migrate some containers from a linux box to an M1 Mac and I’m only having issues with one – a container that connects to a VPN. Everything else seems to work flawlessly.

    I’m getting errors saying that the tun device doesn’t exist – specifically:

    \> modprobe: FATAL: Module tun not found in directory /lib/modules/4.19.121-linuxkit

    Does anyone know if this is an M1 issues? A Mac/Big Sur issue? Trying to track down the error messages aren’t really getting me anywhere. Has anyone successfully made a container that can connect to a VPN?

    Reply

Leave a Comment