6 ms·
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 i
by munro 6y ago
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 is I have to give up a bunch of RAM to the VM that my containers may or may not use, instead of sharing with the host like on Linux.
- jcollins 6y agoDocker Desktop already ran on Macs. This is specifically for the new Apple Silicon support (M1). It's not native, technically, but it feels native the way Docker Desktop works. Basically they manage the VM for you, so you don't have too.
- dalacv 6y agoCan this run a container of windows on Mac M1?
- thefourthchime 6y agoYou can run Windows For ARM on M1 Macs right now, I doubt you can get docker to do this without lots of manual effort.
- gigatexal 6y agoGot a link to proof of this?
- deleted 6y ago[deleted]
- my123 6y agohttps://www.mail-archive.com/qemu-devel@nongnu.org/msg766282.html https://www.mail-archive.com/qemu-devel@nongnu.org/msg766282... for the Qemu patches and https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewARM64 https://www.microsoft.com/en-us/software-download/windowsins... for downloading the Windows build
- dalacv 6y agoQuestion, is there persistence with that? Or are changes lost once it is closed?
- BillinghamJ 6y agoI've been using the ACVM app with. Windows 10 VMDK file. Changes are indeed persisted to the VMDK
- my123 6y agoNo nested virtualisation present currently, as such no virtualization support provided to VMs, so on Windows on an M1 only WSL1 works. Docker Linux containers on Windows require WSL2 instead. Docker Windows containers aren't available on arm64 Windows yet, but stay tuned...
- jsjohnst 6y agoCan you run a container of Windows on an x86 machine? The answer is no, and for the same reason it won’t work on ARM. A “container” is not a virtual machine, you can only run the same Linux executables you would on a normal Linux system. That said, as another person commented, you can run Windows for ARM in a VM on an Apple M1.
- diveanon 6y agoIt doesnt feel native at all, performance and networking are very suboptimal. Haven't tested it on M1 yet, but I doubt the networking challenges will disappear.
- jcollins 6y agoThere 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.
- diveanon 6y agoCan 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.
- jcollins 6y agoThe only thing I can say with confidence is that if you're using ARM containers it is really fast, probably thanks to the Apple Silicon. I imagine memory consumption is on par with running on Intel. I don't think Docker Desktop can really change that.
- diveanon 6y agoHonestly memory is the primary constraint for most of my mac devs running our docker envs.
- jontro 6y agoUnder the hood there is a linux vm running.
- munro 6y agoDang, wishful thinking that they were going native on M1. ;_;
- diveanon 6y agoToo 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.
- gigatexal 6y agoYou wanted Apple to add container support to the OSX kernel? Hah. I wonder if the virtualization API that Apple is pushing performs better than Hyperkit.
- stephenr 6y ago> HyperKit currently only supports macOS using the Hypervisor.framework. Do people really not know how shit works these days?
- shimylining 6y agoIm confused by this comment? I am running Docker Desktop on Mac and have multiple containers running?
- diveanon 6y agoIt is running in a vm
- paxys 6y agoDocker has never needed a VirtualBox VM to launch containers on your Mac. It does its own virtualization internally, and will continue to do so.
- Wowfunhappy 6y agoIt actually did at one point; before Docket Desktop there was “Docker Toolbox”, which required separate virtualization software. The installer came with Virtualbox by default, but there were options to use Parallels and VMWare as well. This is probably what GP is thinking of. I'm actually using a version of this setup today in order to run Docker on OS X 10.9.
- outworlder 6y ago> 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.
- my123 6y agoThey have containers already in a sense, whatever the iOS Simulator.app uses is not VMs, and it's a container in more ways than just one.
- astrange 6y agoIt's a launchd namespace. It's not meant to be secure in the same way a container would be, but it could be used for something.
- BillinghamJ 6y agoThat is not exactly designed to deliver any kind of isolation though - it just runs normal processes
- ploxiln 6y agoI used docker inside a vagrant+virtualbox VM running ubuntu, on macOS, for a few years. It's more reliable, and more debuggable, than docker for mac. It's some easy-auto-transparent storage and networking layers that make docker-for-mac so flaky.
- GGfpc 6y agoSo you have your setup documented anywhere?