Docker Compose V2 no longer working with Monterey v12.6

docker / for-mac

Bug reports for Docker Desktop for Mac

https://www.docker.com/products/docker#/mac

2.44k stars 117 forks source link

Docker Compose V2 no longer working with Monterey v12.6 #6482

Closed ribeaud closed 2 years ago

ribeaud commented 2 years ago

[ x] I have tried with the latest version of Docker Desktop
[ x] I have tried disabling enabled experimental features

Expected behavior

Docker Compose V2 option is checked and working on macos Monterey.

Actual behavior

Docker Compose V2 is NO longer working with the latest Monterey release (v12.6). I am not able to use my mac and I have to perform a hart restart.

Information

macOS Version: 12.6
Intel chip or Apple chip: Intel
Docker Desktop Version: 4.12.0

I can provide more info if necessary/needed and if you're not able to quickly reproduce the problem. This is what I get when executing Docker Compose V2 before the problem starts to appear and somehow blocks the laptop.

ManojBayyapureddy commented 2 years ago

Having the same issue with latest version of Docker

macOS version : 12.6 Macbook Pro M1 pro chip

trungutt commented 2 years ago

Hi @ribeaud, according to the log provided

=> ERROR [registry.gitlab.com/biomedit/portal/frontend:4.6.0-dev.38 internal] load metadata for docker.io/library/node:16-alpine 30.6s
=> ERROR [registry.gitlab.com/biomedit/portal/web:4.6.0-dev.38 internal] load metadata for docker.io/library/python:3.10-slim 30.6s

I'm not sure that there's something to do with compose v2 and MacOS 12.6. Please reopen the issue if needed

ribeaud commented 2 years ago

Hi @trungutt. How could we identify the culprit then?

djs55 commented 2 years ago

I am not able to use my mac and I have to perform a hart restart.

This sounds like a macOS issue, especially since it started happening after a macOS upgrade. It shouldn't be possible for Docker Desktop to cause macOS to hang since Docker does not use kernel extensions etc. Could you take a look to see if you have any panic reports as described here: https://discussions.apple.com/thread/251339518?answerId=252594492022#252594492022

Also check to see if you have non-Apple kernel extensions loaded e.g.

$ kextstat | grep -v com.apple
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>

ribeaud commented 2 years ago

OK, thanks. I will give another try later this week and will let you know.

ribeaud commented 2 years ago

I just made some tests:

I do no have any panic files at given location, mainly .diag files
kextstat | grep -v com.apple:
Use the new Virtualization framework does NOT work (see attached report)
Activating Kubernetes works

BUT Use Docker Compose V2 still does NOT work in my case. Getting following output:

before computer starts to behave strangely...

docker-robott commented 2 years ago

Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.

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. /lifecycle locked