Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Docker on MacOS is slow and how to fix it

paolomainardi.com

Post reply on HN
Print view View original

141–150 of 211 posts

Re: Docker on MacOS is slow and how to fix it

#141

Post by howinteresting »

inkyoto wrote: post #130
howinteresting wrote: post #126

Earlier quoted context omitted.

Many of the bugs I'm talking about can be reproduced on a completely vanilla system.

You have to be a little bit more specific than that and quantify and itemise the «many» part. Otherwise it is pure speculations, generalisations, arm chair theories and hand waving. What is a «vanilla system»? A brand new laptop? Then the hardware is likely faulty, and Apple will replace the faulty computing contraption or refund the purchase. A brand new install on an existing laptop? Likely a hardware fault, a comp…

This isn't handwaving. I'm talking about bugs in the software (not hardware) with rdars attached. For some of them the bug dates back to like 10.5 or so, and the fix is straightforward, but it just hasn't been done. For others the problem is harder (but still possible) to reproduce, but the buggy component is managed by what has been described to me as "one of the somewhat less competent teams" at Apple, with a track record of "extremely stupid design decisions".

Describing them in more detail will deanonymize me so I'm not going to do that.

Re: Docker on MacOS is slow and how to fix it

#142

Post by kdrag0n »

llIIllIIllIIl wrote: post #140
kdrag0n wrote: post #60

Funny that this came up — shameless plug: I've actually been working on a new Linux+Docker+Kubernetes solution for macOS recently! Already added quite a few improvements over existing apps including Docker Desktop, Rancher, Colima, etc: - Fast networking: 30 Gbps! vs. 150 Mbps with Docker VPNKit. Full VPN compatibility, IPv6, ping, ICMP and UDP traceroute, and half-open TCP connections. - Bidirectional filesystem sha…

Is there any way to join the waitlist for the software?

No formal waitlist yet, but drop me an email (see bio) and I'll let you know when there is!

Re: Docker on MacOS is slow and how to fix it

#143

Post by andirk »

zamalek wrote: post #70
mat_epice wrote: post #54

Earlier quoted context omitted.

My read on it was that this person heard what their coworker has to go through, and has formed an opinion based on that. I understand that climbing Mt. Everest is fairly difficult, despite not having done it myself.

I find how specific coworker complains about Linux while simultaneously demanding to use it pretty contradictory. That's why I am interested in more details.

I think it's fair to say that everyone in a company using very similar hardware and software makes maintenance much easier. But I also think any dev should be supported in at least _some_ Linux environment.

Re: Docker on MacOS is slow and how to fix it

#144

Post by andirk »

josephg wrote: post #80
howinteresting wrote: post #72

Earlier quoted context omitted.

Apple laptops definitely have issues sleeping. https://forums.macrumors.com/threads/macbook-air-m1-doesnt-s... There's a litany of bugs in Apple's software. This often gets hidden because developers use workarounds of various sorts, but if you know, you know. It's honestly embarrassing how buggy Apple software is given the vertical integration you describe. The worst part is that almost all of it is closed source so…

> There's a litany of bugs in Apple's software. Personally, the only problems I've only ever had getting macos to sleep properly has been when I've been running VMs. (Hello docker!) When doing purely OS-local development (which is all I ever do these days, because I value my sanity) macos works great. (So long as you have a recent mac. New macos + old laptop is awful.) But as nice as macos is, XCode is an absolute me…

Thanks for the tip. Hello docker!

Re: Docker on MacOS is slow and how to fix it

#145

Post by 29athrowaway »

vforvendettador wrote: post #31
thunky wrote: post #19

Earlier quoted context omitted.

My preferred fix: don't develop in Mac.

For many Mac is the only sensible option. There's one developer in our company that uses Linux and it's a lot of pain to setup. Mac has the best balance between coding, utility tools and "other work stuff". Windows probably on par if not more for "work stuff" but falls badly in the coding & tooling department. Linux is OK ish for coding and utility but falls behind for "other work stuff" and certainly a pain to just…

And your production environment is Linux, so you will be using Linux anyways and all the testing you do on Mac has differences with production unless you do it in a VM where everything is slower.

Linux is not a pain to setup.

Re: Docker on MacOS is slow and how to fix it

#146

Post by howinteresting »

allarm wrote: post #138
jiggawatts wrote: post #82

Earlier quoted context omitted.

> but falls badly in the coding & tooling department. That's more perception than reality, often from people who simply don't know how to use Windows. Visual Studio, Visual Studio Code, and IntelliJ IDEA blow any Linux text editor out of the water for developer productivity. For Linux workloads there is the Windows Subsystem for Linux (WSL 2), which now even supports GUIs with GPU acceleration! Visual Studio Code can…

> Visual Studio Code can even operate in "remote" mode where it tunnels into a Docker container or Linux server and acts as-if the remote target was the local machine. Of all things in this comment this one is the funniest, because Emacs was able to do it for years (decades?).

If you're talking about tramp, its design is quite a bit worse than vscode's or intellij's remote support.

Re: Docker on MacOS is slow and how to fix it

#147

Post by jiggawatts »

dwaite wrote: post #139
jiggawatts wrote: post #82

Earlier quoted context omitted.

> but falls badly in the coding & tooling department. That's more perception than reality, often from people who simply don't know how to use Windows. Visual Studio, Visual Studio Code, and IntelliJ IDEA blow any Linux text editor out of the water for developer productivity. For Linux workloads there is the Windows Subsystem for Linux (WSL 2), which now even supports GUIs with GPU acceleration! Visual Studio Code can…

Depends a lot on what you are trying to accomplish. The inability to get something akin to VT220 terminal access and shell scripts on a POSIX-based system without resorting to a virtual machine (a la WSL2) is a deal-breaker for me. The steps for using scripting languages (e.g. Node, Python, Ruby) is typically entirely different on Windows than it is from all other server and desktop platforms. For those who can spend…

WSL2 is not a virtual machine, it's a subsystem. It's basically the opposite of WINE.

You can run all of your favourite languages nearly identically to Linux on Windows either via Docker or WSL2.

> Windows requires emulation to run aarch64-based containers. Except on Windows for ARM

Making Windows and Linux the only platforms with ongoing support for both ARM and Intel CPUs, unlike MacOS where Intel support will eventually expire.

Re: Docker on MacOS is slow and how to fix it

#148

Post by YetAnotherNick »

wkat4242 wrote: post #120
i386 wrote: post #109

Earlier quoted context omitted.

Even after building and selling developer tools for a decade, it always surprises and enrages me to see how miserly developers are.

It's also our employers. They don't like to spend money on dev tools because the suits don't see the benefit. There's no glossy Gartner magic quadrant BS for every niche development usecase so they think they're throwing money into the fire.

If you think you get more productive with $10/month or something that most dev tools cost, why don’t you buy it on your own. After all even if it increases your salary hike by 1%, it will be worth it. I have seen designers buying Adobe tools which cost much more than dev tools, and their salary is on average lower.

Re: Docker on MacOS is slow and how to fix it

#149

Post by jeroenhd »

vforvendettador wrote: post #31
thunky wrote: post #19

Earlier quoted context omitted.

My preferred fix: don't develop in Mac.

For many Mac is the only sensible option. There's one developer in our company that uses Linux and it's a lot of pain to setup. Mac has the best balance between coding, utility tools and "other work stuff". Windows probably on par if not more for "work stuff" but falls badly in the coding & tooling department. Linux is OK ish for coding and utility but falls behind for "other work stuff" and certainly a pain to just…

Everyone in my company just uses Windows if they don't want to bother with Ubuntu. Excellent Linux tool chain support, excellent driver support, it just works.

WSL 2 is a game changer because it makes all the Linux centric dev tools available to Windows without setting up virtual machines or other such nonsense, even running graphical applications these days. The only major pain point I've run into (that isn't "I prefer Linux") is the lack of IPv6 support within WSL 2.

If you avoid buying Nvidia hardware, Linux generally "just works", unless you use Windows-only software (which macOS also suffers from) or choose to make your life harder by installing Arch or Gentoo. Ubuntu's snap is a pain for power users who want to hack on their Linux system but if all you want to do is develop or do work stuff, it just works out of the box.

Re: Docker on MacOS is slow and how to fix it

#150

Post by jeroenhd »

maria2 wrote: post #53
zamalek wrote: post #41

Earlier quoted context omitted.

> everyone in the development & support team uses Mac (except this one guy who insisted in Linux), > certainly a pain to just keep it updated. > Linux and it's a lot of pain to setup. If you're not using Linux, how are you justifying these claims? > certainly a pain to just keep it updated. Excluding the boot time for both, MacOS takes between 15 and 45min to update. Linux is a few seconds. I suspect that the only OS…

How do I get my laptop to properly sleep when using Linux?

Personally, I close the lid of my laptop, though the Fn-key shortcut is sometimes better.

Sleep is one of those things that have always just worked for me, at least on Linux; in Windows, I've had to deal with random wakeups after some kind of Windows update. That said, with less than 30 seconds from off to IDE I don't tend to use sleep all that often.

Post reply on HN