Hello,
Docker support for M1 mac is now out on the preview version.
Thought you guys would like to know !
Docker support for M1 mac is now out on the preview version.
Thought you guys would like to know !
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Docker support available on the preview !
- Thread starter Jinbei
- Start date
- Sort by reaction score
where can we download the preview version? I had a look and didn't find it. will I gain access after registerign for the preview program?
Here you go:
Developer Preview | Docker
Join the Docker Preview Program to work with our team and help shape the future of the developer workflow experience.
www.docker.com
TL;DR: yeah, you'll gain access after registering for the preview program.
Considering recent work to get the hypervisor working with VMs... and having QEMU working almost perfectly (some kinks here and there), I'd actually be surprised we don't see anything from Docker/Parallels/VMWare soon.
But still, I have to admit that this is super exciting, and it means full compatibility may not be too far off.
you mean the Docker M1 preview? disk I/O is as slow as it is with vftool and/or SimpleVM. apart from that, so far it just works.
How long did it take for you to receive the Slack invitation? I am waiting for that now.
Looks like tech preview is ready to download: https://www.docker.com/blog/download-and-try-the-tech-preview-of-docker-desktop-for-m1/
Still haven't managed to make my app communicate with a separate Chrome/Selenium container though (works fine on Intel)
I didn't manage to get Selenium to work with neither a separate Chrome container nor Chromium installed in my app image. I am now using Cuprite instead of Selenium for my Rails app with Chromium installed in the image. Curprite uses CDP to connect directly to Chrome or something like that. Works fine.
According to the docs there should be an internal dns host.docker.internal that resolves to the internal IP address used by the host. I can't get this special host name to work.
But I was able to use the /24 network defined by Preferences->Resources->NETWORK to get curl in a linux container to talk to nginx in a container on port 80. That should be enough to get Selenium running. You just have to figure out the IP. For me I started nginx up first and it resolved to 192.168.64.1. I'm assuming it is dynamic though and you can't rely on that.
Edit: I was also able to get an amd64 instance running. All I executed was "uname -m" but it seemed very fast. I don't know enough about Docker yet to evaluate if this means that amd64 containers will be fast enough for general use.
I *think* my problem is due to the fact that I am using network aliases for my app container (to be able to test stuff with custom domains). So that's related to DNS too. All in all as a preview version it's awesome.
I haven't reported the problem to Docker with host.docker.internal but I will. I suspect that many people will notice the problem.