AuthorDustin ArchivesCategories |
Back to Blog
Docker For Mac Native10/27/2021
Docker Desktop for Mac on Apple silicon is now available as a GA release. Estimated reading time: 4 minutes. Docker can Docker Desktop for Apple silicon. While users could previously use Docker on Windows and Mac, the packages remove additional layers of dependencies and offer native, tightly integrated user experience. Docker has launched a beta of Docker for Mac and Docker for Windows, two software packages that represent significant software architecture changes made to optimize Docker for an OS-native experience./mvnw verify -Pnative -Dquarkus.test.native-image-profiletest.However, don’t forget that when the native executable is. For example, in your application.properties file, add: quarkus.test.native-image-profiletest.Alternatively, you can run your tests with. This can be overridden using the quarkus.test.native-image-profile property.In the example below, the Applications folder is in grid view mode. Double-click Docker.app in the Applications folder to start Docker. Double-click Docker.dmg to open the installer, then drag the Docker icon to the Applications folder. Set In Preferences, Docker the API URL: unix:///var/tmp/docker.sockInstall and run Docker Desktop on Mac.This is a non-issue using Docker on Linux (there's one file system with isolation controls, no VM, no sync), but appears to have similarly painful consequences for Docker for Windows (using WSL2).As others have said, barring "just develop on Linux" there's no one-size-fits-all answer to this, your use case may allow choosing a set of compromises that works for you, but they're probably going to hurt for someone else.I'm voting for this issue to be closed, because there is no "issue" or actionable metric to take - it's just an umbrella "make things faster".As pointed out within this thread, there are numerous separate tickets which can be created, but they need actionable metrics to be deemed it to be "complete", and we need to draw out specific use-cases to consistently replicate a certain metric. This picture is worsened because the UX of Docker for Mac works hard to ensure developers can use it oblivious to the existence of HyperKit. Because Docker is fundamentally a linux based technology, that means we need the HyperKit VM (or some other compatibility layer) to provide that environment.IO performance within the VM is likely very fast - the hard problem is that we expect to treat the host file system as the source of truth and that means some form of sync strategy working across the host/VM boundary, this has overhead and so we find ourselves choosing between different compromises around consistency/eventing/delay, docker-sync at least makes some of these more explicit. The reasons that can even happen are interesting, but a digression here.The problem Docker is trying to solve here is fundamentally harder though - the promise is that we get to develop in our local file system, using tooling running natively on MacOS, but have our containers run in an environment consistent with other platforms.
Docker Native Mac On AppleThey may just not have the developer hours available to properly address this issue. Despite this thread having accumulated several hundred comments, we're a relative minority of their userbase. Add support for NFS (this belongs in a ticket all by itself so there can be a separate side-discussion relating to this specific sync method, without the need to bash other sync methods, having opinionated debates about which sync method is better, etc.).Does anyone else agree? Otherwise, this ticket is completely un-actionable, and will never be resolved or closed.I'm voting for this issue to be closed, because there is no "issue" orActionable metric to take - it's just an umbrella "make things faster".As pointed out within this thread, there are numerous separate ticketsWhich can be created, but they need actionable metrics to be deemed it toBe "complete", and we need to draw out specific use-cases to consistently- osfx has increased filesystem latency with projects over 50,000Files (actionable metric: define beginning latency in ms, then defineExpectation of latency this file sync method).- gRPC delays writes for X-ms for projects containing more than 500- Add support for NFS (this belongs in a ticket all by itself so thereCan be a separate side-discussion relating to this specific sync method,Without the need to bash other sync methods, having opinionated debatesAbout which sync method is better, etc.).Does anyone else agree? Otherwise, this ticket is completelyUn-actionable, and will never be resolved or closed.You are receiving this because you were mentioned.Reply to this email directly, view it on GitHubThe evidence you mention can be interpreted in different ways.That was just one of the many pieces of evidence in this thread.Oh plenty of reasons. gRPC delays writes for X-ms for projects containing more than 500 files of 50MB in size. Why they didn't just leave it in as another checkbox you could enable, like the one for switching between osxfs and gRPC, I don't know.On Mon, at 11:15 AM Robert Rollins wrote:Oh plenty of reasons. But they took it out for reasons having something to do with it hurting other people's experience in some way. It worked great for me, slicing my page load times by about 75% compared to osxfs and about 90% compared to gRPC. I'm sure they're quite sick of seeing this thread being bumped to the top of the issue queue, actually.There was even a (mostly) working solution available for a single point release, known as Mutagen. Grandia saturn english patchButThey took it out for reasons having something to do with it hurting*other* people's experience in some way. It worked great *for me*, slicing my page loadTimes by about 75% compared to osxfs and about 90% compared to gRPC. I'm sure they're quite sick ofSeeing this thread being bumped to the top of the issue queue, actually.There was even a (mostly) working solution available for a single pointRelease, known as Mutagen. They mayJust not have the developer hours available to properly address this issue.Why else do you think this thread has been going strong for well over aYear with next to no word from the actual developers? I think they've made*maybe* 5 or 6 comments on this thread.
0 Comments
Read More
Leave a Reply. |