Does this mean I can run containers natively on Mac? And I don't need a VirtualBox VM running on my Mac to launch containers? This would be huge for me, and is always a big in my mind why I would consider switching back to Linux. Edit: Docker on Mac has never felt as snappy as on Linux, because of the VM, though I have no hard numbers. Networking is a PITA, but it's not hard to figure out. The other main thing I hate…
> Docker on Mac has never felt as snappy as on Linux It's extremely slow compared to Linux and I'm pointing my fingers at the virtualization layer without any hard evidence because it's the most likely suspect. With all this focus on sandboxing apps of late, I'm wondering how far the OSX kernel is from having a feature set that resembles cgroups and network namespaces.
Tech Preview of Docker Desktop for M1
51–60 of 231 posts
Re: Tech Preview of Docker Desktop for M1
#52Earlier quoted context omitted.
There is overhead for sure but if you use x86 containers on an Intel Mac or arm64 containers on an Apple Silicon mac, it's pretty performant.
Can you share any details on M1 perf and resource consumption? Docker vm on mac is noticeably slower and consumes a lot of resources in my experience.
I imagine memory consumption is on par with running on Intel. I don't think Docker Desktop can really change that.
Re: Tech Preview of Docker Desktop for M1
#53Earlier quoted context omitted.
Too bad, if they had it running natively I would actively consider switching back to mac. Glad to see they are making progress on the M1 port though, my team will be excited.
If Docker for mac was running natively it would be more or less useless. Nobody deploys production code on MacOS hosts anymore. That it is all so smoothly powered by Linux is what makes it a great product.
If apple gave a shit about non apple developers they would provide the kernel hooks to help make it possible.
Also, nobody deploys on mac hosts because virtualizing macos in a cloud environment is against tos, so options are expensive and limited.
Re: Tech Preview of Docker Desktop for M1
#54This bit about Multi-platform development is most interesting to me. > Many developers are going to experience multi-platform development for the first time with the M1 Macs. This is one of the key areas where Docker shines. Docker has had support for multi-platform images for a long time, meaning that you can build and run both x86 and ARM images on Desktop today. If multi platform images work, a lot of the concerns…
i have high hope for AMD/TSMC to push x86. Intel seem to be...stuck for now.
Re: Tech Preview of Docker Desktop for M1
#55In my experience Docker Desktop has been such a resource hog, and Apple's hypervisor implementation pretty poor. I much prefer to have all that heavy lifting isolated away from my development machine to keep it responsive and cool.
Re: Tech Preview of Docker Desktop for M1
#56Absolute disaster, this platform. The opacity and lack of early availability for development made for a really ugly adoption experience. I feel that people should not encourage this and vote with their money in the DevOps / Dev sector to discourage other companies from pulling the same stunt.
Compared to the PPC->Intel transition, this is a cakewalk. Compared to Microsoft's (multiple attempts) to migrate to ARM, this is a true triumph.
Re: Tech Preview of Docker Desktop for M1
#57[1] - https://www.docker.com/community/get-involved/developer-prev...
Re: Tech Preview of Docker Desktop for M1
#58Earlier quoted context omitted.
Too bad, if they had it running natively I would actively consider switching back to mac. Glad to see they are making progress on the M1 port though, my team will be excited.
... if docker ran “natively” it’d mean using kernel hooks provided by xnu, which means you’d be able to run another instance of macOS in a container. How is it so many people use docker but have zero fucking clue about how it works?
This is not true, for multiple reasons. Strictly speaking it only means you'd be able to run another instance of Darwin in a container. And, as you surely know because your tone of voice implies you bear immense knowledge, a Docker-style container is not a full OS: it doesn't run an init or normal system daemons, so it wouldn't even be a full instance of Darwin, so it wouldn't have to support functionality only needed by launchd or system daemons (e.g. WindowServer). It would just need to let you run a stanalone program in a chroot + separate network, PID, and IPC namespace + apply resource controls.
Furthermore, since most people are using Docker for developing software that's going to run on Linux, there would be no real need to virtualize the parts of XNU that aren't also provided on Linux - notably all the Mach stuff. You'd just need to provide a BSD-style syscall API to programs in a container.
Re: Tech Preview of Docker Desktop for M1
#59Absolute disaster, this platform. The opacity and lack of early availability for development made for a really ugly adoption experience. I feel that people should not encourage this and vote with their money in the DevOps / Dev sector to discourage other companies from pulling the same stunt.
Lack of early availability? They sold $500 dev units specifically for this purpose.
Re: Tech Preview of Docker Desktop for M1
#60Absolute disaster, this platform. The opacity and lack of early availability for development made for a really ugly adoption experience. I feel that people should not encourage this and vote with their money in the DevOps / Dev sector to discourage other companies from pulling the same stunt.
Docker or M1 macs?