Docker for Mac tests improved I/O performance for shared volumes
1 points · Open discussiondocker
for-mac
Systems & Infrastructure2016–2026
docker / for-mac
for-mac
Bug reports for Docker Desktop for Mac
86Distinct people
95Mentions
1Explicit recommenders
2.5KGitHub stars
What to know before exploring
What it is
Bug reports for Docker Desktop for Mac
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
I spent close to 12 hours yesterday trying to get a fairly simple node app to run on my mac yesterday. Turned out I had to wipe out docker completely and reinstall. Keep in…
dawnerd used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 5:03:38 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year95 dated mentions
Observed mentions: 2016-07-29 13:01:41 UTC to 2026-01-30 01:28:34 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 9 | 2 | 7 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 7 | 0 | 7 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 32 | 13 | 19 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 18 | 4 | 14 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 5 | 4 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 11 | 8 | 3 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 2 | 1 | 1 |
From the project README
An excerpt from the repository, fetched Nov 12, 2026.
Read the project’s introduction
Docker Desktop for Mac
NoteThis repository is being sunset in favor of desktop-feedback.
Existing issues will remain here but will be moved to the new repository as they are updated.
Getting Docker Desktop for Mac
Docker Desktop for Mac is free to download.
Documentation
If you don't understand something about Docker Desktop for Mac, the extensive
documentation is a great place
to look for answers.
Support
Support for Docker Desktop is available to Docker customers on a Pro or Team plan
by completing the Desktop support form.
Bugs with the Docker Desktop for Mac software can be filed as issues in this
(docker/for-mac) repository, which we respond to
on a best-effort basis. Support requests in this repository (i.e., trouble installing
or using the software) will be ignored, but community support is available from the
Docker community Slack.
This Repository
This repository contains an issue tracker for Docker Desktop for Mac -- an
integrated Docker experience on OS X or macOS. If you find a problem
with the software, first browse the existing
issues or search from the bar
at the top (s to focus) and then, if you don't find your issue, open
a new issue.
Component Projects
Docker Desktop for Mac uses many open source components. A full list of
components and licenses is available inside of Docker Desktop from About Docker Desktop -> Acknowledgements in the 🐳 menu.
Some notable components include:
HyperKit, a toolkit for
embedding hypervisor capabilities in your application
DataKit, a tool to orchestrate
applications using a 9P dataflow
VPNKit, a set of tools and
services for helping HyperKit VMs interoperate with host VPN
configurations
Read the full README on GitHubWhat Hacker News says
18 sourcesDocker for Mac – VirtioFS Support (latest comment)
1 points · Open discussionIt’s not like we haven’t been trying! Just see how these map to the issues I originally mentioned:
https://github.com/docker/for-mac/issues?q=is%3Aissue+is%3Ao...
In The Magic Behind the Scenes of Docker DesktopI'm a happy user of Docker Desktop myself (as a personal user) so Enterprise is not the first thing that came to mind when I read your comment. Sorry for misinterpreting.
In that case, seems fair enough that as a business suddenly being asked to pay for Docker Desktop, you'll start asking for a more polished experience.
But they've already done the incredibly hard part which is creating and popularising OCI, developing an engine that works on most operating systems, and having nice tooling around all of that.
Polishing the Docker Desktop experience should be fairly easy as soon as people let the Docker devs know how they expect it to work: https://github.com/docker/for-mac/issues
In The Magic Behind the Scenes of Docker DesktopThe Docker daemon (likely the HyperKit VM) on the Mac has a tendency to burn CPU cycles, even when there are no containers running. It's pretty common for it to sit at 10-20% of a core all day, and sometimes gets pegged at 100% until you quit.
There are countless closed issues in the GitHub issue tracker [1] for similar issues, but the symptoms don't seem to go away for me or many of my colleagues.
It's been a pretty awful experience on Mac for a long time, so any competition is surely welcome.
[1] https://github.com/docker/for-mac/issues/3499
In How to Replace Docker with Podman on a MacFrom looking over your Vagrantfile it looks like the project files are mounted from the host into the VM so ssh would only be required for tunneling to the db connection? (Although that can also be avoided by exposing a port or using bridged networking).
The biggest issue I've found with this kind of setup is that file change events from the host don't cascade to the virtual machine using VirtualBox's shared folders. NFS handles this better (still seconds delay based on cache values) but that is then a problem for Windows users.
It's been a few years since I switched to using Linux natively so my knowledge on Docker for Desktop Mac mount strategies may be out of date, but at one point docker introduced options such as :cached and :delegated which can have a considerable improvement to container file access speeds. Additionally, I've heard
Read the rest
of people using mutagen and nfs for significant improvements, but I've never tried that setup. Here's a long discussion about it: https://github.com/docker/for-mac/issues/1592#issuecomment-6...
I opened this ticket 3.5 years ago and they still violate GDPR https://github.com/docker/for-mac/issues/2122
In Ignoring Docker updates is a paid feature now?We are trying our best to move away from docker for mac for a couple of reasons:
1) Years of CPU/Battery hogging (https://github.com/docker/for-mac/issues/3499) After the fix, this seems to regress every few releases (https://github.com/docker/for-mac/issues/5567)
2) Docker for Mac has made the user hostile decision to force updates unless a user opts for a paid plan. Due to this decision, and a bug with 3.3.x (https://github.com/docker/for-mac/issues/5572) which indicates a 500 error under unusual circumstances, downgrading and staying at 3.2.x on a free plan is not possible. I believe this issue runs even deeper, because proxies I've used for years are returning an errant EOF on a configuration that works fine on 3.2.x.
I don't have enough time to wrestle with these tools, and even with docker-compose our local environments aren't very
Read the rest
close to production because of the lack of kubernetes orchestration (admittedly have not tried much through docker for mac, but I'm surprised there isn't a closer-to-metal solution). I currently maintain a number of proxy configurations to make our local setup work, and if I'm going to move to a paid tool, I want to make sure its the right fit.
EDIT:
This sounded more unappreciative than I meant it to. I think the docker for mac team are doing an awesome job and that it's a hard product to create and maintain. I appreciate that they are attempting to monetize it and do think it's something we should pay for. I just don't like the way they chose to implement their monetization.
I tried using docker for x86 builds for Lambda (which doesn't support ARM), and hit this brick wall, unfortunately:
https://github.com/docker/for-mac/issues/5123
I went and checked the issue when i saw they've made a formal release but it doesn't appear to be resolved. So maybe keep it in mind if anyone has issues trying to use docker now :)
Edit: I see Docker has closed the issue and encouraged people to simply use ARM containers instead. Unfortunately that's not an option for cross-compilation when you're using x86 servers. Something for people to keep in mind when deciding what laptop to buy next, i guess.
In Docker Desktop for Mac (Apple Silicon)(I work for Docker on the M1 support)
I'm glad it's working for you! There's a bug in the recent Docker Desktop on Apple Silicon RC build which affects some users of vagrant at the provisioning stage when the new ssh key is copied into the machine. It turned out that the permissions of `/dev/null` inside `--privileged` containers were `0660` (`rw-rw----`) instead of `0666` (`rw-rw-rw-`) In case you (or someone else) runs across this there's an open issue with a link to a build with the fix: https://github.com/docker/for-mac/issues/5527#issuecomment-8...
In M1 dev setup with a virtual Linux boxDocker – host.docker.internal does not resolve properly
1 points · Open discussionNo. We're still on the last stable version (2.5.0.1)
Every version after that either doesn't start [1] or makes random containers miraculously stop working.
The 2.x version has your CPU burning, but that seems to persist in 3.x [2].
I stopped trying after they pulled in the auto-upgrade feature. Our team has no time playing bug-hunt easter egg at random times.
I honestly don't comprehend how this software gained such a wide adoption on Macs.
Docker on Linux works flawlessly meanwhile.
[1] https://github.com/docker/for-mac/issues/5146
[2] https://github.com/docker/for-mac/issues/5116
In Please don't upgrade Docker without asking firstYou can't, when you're on a Mac and your code is bind-mounted into the container. This is the most comfortable method of development for me, and works perfectly on Linux. https://github.com/docker/for-mac/issues/3677
In Docker for Mac M1 RCOuch ... ~10x slower ????
https://github.com/docker/for-mac/issues/5389
from a github comment:
"Such a surprise every time I import a database to see it run about 10x slower than amd64."
In Docker for Mac M1 RCI ran into [this](https://github.com/docker/for-mac/issues/5208) bug just today - mentioned in the release notes.
If you're using a VPN (in my case, the NextDNS client), you might want to de-select the option to start Docker on boot. Start it manually instead once your VPN client is loaded and connected. In my case a failure to do this would completely bork the ability to connect to the internet - either over ethernet or WiFi. Took me a while to figure out what the cause was.
In Docker for Mac M1 RCShowing the 15 most recent of 18 sources. Enable JavaScript to search and browse every indexed mention.