7 ms·

Under the hood there is a linux vm running.

• munro 6y ago
  Dang, wishful thinking that they were going native on M1. ;_;
• diveanon 6y ago
  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.
  • gigatexal 6y ago
    You 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?
      • monkpit 6y ago
        It’s great that you know about how Docker works. How about being a little more informative in your comments here?
      • recursive 6y ago
        If you've got something to say, just spit it out.
      • macintux 6y ago
        Your hostility towards everything and everyone doesn't engender productive discussions.
  • stephenr 6y ago
    ... 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?
    • haswell 6y ago
      Docker obscures the implementation details. Part of this is by design: don't worry about the hard stuff, because Docker does it for you. It's completely unsurprising that many folks haven't spent the time to dive into the internals. In many cases, because they don't need to. Such is the nature of abstraction and higher level frameworks.
      • outworlder 6y ago
        We aren't even close to a point where someone can just pretend a container is a magical box that just works. All abstraction leak. This is a relatively recent, quite leaky one.
        • haswell 6y ago
          > We aren't even close to a point where someone can just pretend a container is a magical box that just works. I challenge this assertion. While it is of course true that there are situations that require a deeper knowledge of Docker, this is also not universally true. Many projects these days have a Getting Started doc that has some options like: - Build from source - Install this package - Use Docker I often choose the Docker option because I know I'll (most likely) get a working version of the project in 5 minutes with minimal effort. I might not even fully understand the project yet or its architecture (much less that of Docker), but I can get it up and running with `docker pull` and `docker run`. In many cases, I'll never need to know anything more. I've personally spent more time using docker to build my own stuff, so I've had to learn more. But for many folks, it absolutely is a magical box that just works, and that's perfectly ok. I agree that all abstractions tend to eventually leak. But depending on why you're using Docker, you may never have a reason to encounter that leakage.
      • 6y ago
  • paxys 6y ago
    Docker can't run natively since it uses linux kernel features not available on a mac. Apple would need to do a lot of work first to make it happen.
  • perbu 6y ago
    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.
    • diveanon 6y ago
      I develop exclusively on Linux, but it would be nice if my teammates who don't didn't melt their laptops doing local dev on mac. 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.
      • ehutch79 6y ago
        I deploy on linux, but dev on macOS without a vm or docker or anything. If you're not doing anything OS dependant, which most web apps don't, you can run everything natively.
        • diveanon 6y ago
          Isolation is another important reason people use docker. I don't want my developers to have to manage a complex dev stack and it's dependencies. I would argue that this is the primary use case for local docker dev these days.
      • perbu 6y ago
        Me and I just about everyone I know that has a mac develops _for_ Linux. What is nice is that I can push, pull and run Linux images on my mac. If the containers where native Macos docker images it would be about as useful as native Docker on Windows. Which I'm sure is great for the few ppl that need it - but pretty useless for most ppl. But I sure wouldn't mind if was a bit snappier. But it is plenty fast enough for my needs atm.
        • diveanon 6y ago
  • munro 6y ago
    People griefing about to you that you have no idea what you're talking about, smh, don't listen to them. All I have to say to them is: look at the Wine project running Windows software natively on Linux. Don't underestimate nerds who have a vision in mind. And look at Kubernetes deprecating Docker. At the highest level of application development, all these details don't matter. I'm using all GNU command line tools compiled for my Mac, I'm sure we could figure something out to increase containerization efficiency on Mac. ¯\_(ツ)_/¯