Docker for Mac hangs constantly #1835
Comments
|
I am also having this same issue. Diag 11EED9F3-181B-41BC-A99D-BEF7DDC1580E |
|
Same issue. I have 4 CPUs/6GB RAM allocated. |
|
Still seeing this non-stop. It's sufficient to run |
|
Sadly, I can confirm that since a few weeks docker for mac is far less stable than it used to be. It randomly crashes and only a mac reboot helps to bring back the service. Manually restarting the service doesn't work. |
|
Also having this issue. However I have noticed that starting a new Diagnose process tends to unblock the process. However I am using a custom container I am building. Restarting the app does help but you have to kill both the hyperkit process and the qcow-tool process. A53027AC-01D5-42AC-BBEB-2B7C58218846 |
|
Installed docker on new MBP and after mac woke up from sleep, I noticed this issue. I have not noticed this on my previous MBP.
Diagnostic ID: |
|
Please, try a more recent version of Docker for Mac. |
|
@akimd I just tried again with the latest edge, 18.01.0-ce-mac48 (220004). The exact same thing still happens. Diagnostic ID: |
|
I had the same issue with docker 18.02-ce. After executing for a interval, some subcommands as 'docker-rmi' hanged forever |
|
Having this same issue. Do we need to open another issue? |
|
Hi guys, No, there's no need for another issue, thanks! We need to understand what is going on here and fix it. Currently we're busy preparing the next releases, we will be back to this issue as soon as possible. Thanks for your help! One question though: are you running qcow or raw images? What does give? |
|
Thanks for reopening this issue! For me, that command shows a |
|
You don't need to update to raw. As a matter of fact I was asking because we found raw disks to be less reliable so far, and I was wondering if it could be related to your problems. No, we don't migrate from qcow2 to raw, it's only when starting anew that raw might be chosen. |
|
+1 ... I'm having the same issue. Docker for Mac is a better experience than virtual box was, what without the intermediate VM and all, but this makes it torture. Of course, when it's hanging diagnostics doesn't work. But this is what it says when everything's working: Diagnostic ID: (incidentally, The And this is an APFS volume, if that matters. |
|
Still seeing this in 18.03.0-ce-rc1-mac54 (23022). Usually when this happens, trying to restart or quit-then-start Docker via the Docker for Mac GUI will hang in the "Docker is starting" state, and I have to force quit the Looking around for other solutions, I came across docker/compose#3633, which points (at the end) to moby/moby#35933. This may not be the same issue as what I'm experiencing since people there report that rolling back to 17.09 fixes the issue for them, while I was already experiencing this problem in 17.06. I don't believe that I'm seeing this due to tty, resource, or network issues either. |
|
@ryanfb Thanks for the pointers, these issues are interesting. I can't reproduce the behaviour. Could you submit a Diagnostic using the latest Edge (mac54 is good)? |
|
Diagnostic ID: I've been trying to dig deeper into this over the last couple days - one thing I've been checking is what's going on inside Docker by using Since then I've done a few factory resets - after the first of these, I could no longer disable trim per the instructions in this comment, since
|
|
On my machine |
|
Hello, I'm also having many issues with the latest Docker version. It takes about 2 min to start although only 1 small dnsmasq service is configured to start along with Docker. When waking up the mac, docker-compose timeouts when stopping or restarting a stack. Only "fix" is to restart Docker which is another 3 min wait... |
|
Almost by accident, I think I've discovered a workaround for my particular case. I decided to try running the same This gave me the idea to try the same thing on my iMac today - and after moving the Docker disk image off the internal 3TB Fusion Drive to an external USB drive, I seem to be able to do everything I need to do without having Docker crash or become completely unresponsive. All drives (internal and external) are formatted Mac OS Extended Journaled (case-insensitive), and the internal drives report a S.M.A.R.T. status of "Verified" with no other programs appearing to have issues using them. Perhaps this is consistent with the ATA/SCSI errors causing a CPU/task stall in my logs above, though I'm not sure what the root cause or error is. The thing consistent across both machines is that the problematic drive for Docker is an internal SSD or Fusion Drive. |
|
@ryanfb thanks for the logs above. I extracted the logs from the diagnostics and, for now, just add them here for completeness as there actually were some relevant error messages before the hung task messages: So this indicates some hang/timeout in the hyperkit blockdevice layer (or further down in the qcow2 code). We had related issues in the past (see moby/hyperkit#94). @ryanfb you mentioned that your MBP is relatively under-resourced and may have been close to running out of diskspace but also said your iMac has 3TB drive and you had the same issue there. Is the drive in the iMac also close to full? I've not been able to repro this locally with the two cases you mentioned above |
|
The 3TB drive in the iMac has/had about 400GB+ free when I was encountering this problem. In the Docker for Mac UI the disk image was sized to ~200GB with ~20GB used on disk. The MBP is under-resourced in terms of memory/CPU - only 8GB (vs. 32GB in the iMac) and a slower/older CPU. |
|
+1 Couldn't even get a diagnostic. |
|
Can someone reproduce it with 18.03 (stable or edge) and post diagnostics please? |
|
@akimd |
|
I confirm I have the same issue as @dhinojosa in the same version above (latest version currently). It seems related to Kubernetes as I also reset Kubernetes Cluster settings but the same issue. |
|
There is a magic solution here #4239 (comment) until it's get fixed properly. |
|
BTW, the latest version works like a dream. Version 2.3.0.5 (48029). I no longer have the issue and I can start and stop Kubernetes with ease.
|
|
Updated to 3.0.1 this morning and now everything is completely stucked. Had to reset to factory settings and rebuild all my images just to be able to run one. After a very short while, can not run commands and get hung. |
|
We've been experiencing these types of freezes at an increasing rate. It's gotten so bad that it almost feels like we're running some unstable nightly build! Suggested things tried, unfortunately to no effect:
Some observations:
Perhaps related:
What can we do to help troubleshoot this? |
|
@pcjmfranken We are not getting widespread reports of this, so I would suspect something specific to your environment. Maybe some corporate security software is interrupting the network path for example? |
|
@stephen-turner I'm genuinely happy to know that it seems to be working just fine for most! Someone from ops will be helping us investigate early next week. Findings will be reported back here. |
|
Thanks, I look forward to hearing the results. |
|
@pcjmfranken any updates? It seems I encountered the same issues, reverted to v2.3. Now kind of scared to upgrade again. |
|
@pcjmfranken any updates? I am running into the same issue. |
|
@wlrd I haven't seen any updates here. Had reverted to 2.3, it worked overall but was often slow. Tried upgrading again and running into similar issues again. Getting tired of this, I have to restart my docker several times a day. |
|
A more recent related issue, specific to mac M1, happens quite regularly, #5590. That one has nothing to do with kubernetes though. |
|
Just discovered some of my mail-in replies were never actually posted! Never managed to pinpoint any causes, but these problems persisted across all environments. The Docker dev setup has since been abandoned by the majority of these projects, as the additional overhead that it brought was becoming too costly. |
|
Same behaviour like @samuelhalff, reverted to v2.3 as well. |
|
3.5.1 same issue here |
|
If you're having trouble on mac M1 and can't run |
@pcjmfranken which container tech have you moved to? |
|
same issues on 3.5.2, |
|
@samuelhalff Good old VMs. This issue persists in the projects that still use a Docker-based development environment. |
|
recently upgraded to this (on MAC) This is now a problem again. sigh. I can volume mount and access it, but as soon as something changes on the mounted volume, and I try to access anything on that mount in the container... it just hangs. I have to restart docker completely to be able to do anything again. EDIT: going to Preferences -> General -> "Use gRPC FUSE for file sharing" actually fixed it and i was able to use volume mounts normally again. Hope that helps someone looking for answers |
|
Issues go stale after 90 days of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
|
this issue needs to be reopened. still experiencing the same issue on 4.1.0 |
|
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
and others
Expected behavior
Docker for Mac doesn't hang.
Actual behavior
Docker for Mac hangs.
Information
Diagnostic ID: BED37CCE-B2F9-41B9-B9E6-72EFEBE30091
Steps to reproduce the behavior
docker-compose up --force-recreatedocker psor any other command that interacts with Docker for Mac.I've tried using
docker system prune, using "Reset" in the Docker for Mac GUI, increasing RAM/CPU allocations (currently 16GB/6 CPU), and upgrading Docker for Mac to edge. I still encounter this problem multiple times per day, and now regularly/reliably when trying to start this Compose file.The text was updated successfully, but these errors were encountered: