Active Incident

Updated a few seconds ago

Incident Status

Operational

Components

Docker Desktop

Locations

Client Machines



January 7, 2025 17:37 PST
January 8, 2025 01:37 UTC
[Investigating] Some users are seeing an issue starting Docker Desktop on macOS where macOS reports that either com.docker.vmnetd or com.docker.socket is malware. The workaround is to: 1. Quit Docker Desktop and check that no remaining docker processes are running using the Activity Monitor 2. Run the following commands: #!/bin/bash # Stop the docker services echo "Stopping Docker..." sudo pkill [dD]ocker # Stop the vmnetd service echo "Stopping com.docker.vmnetd service..." sudo launchctl bootout system /Library/LaunchDaemons/com.docker.vmnetd.plist # Stop the socket service echo "Stopping com.docker.socket service..." sudo launchctl bootout system /Library/LaunchDaemons/com.docker.socket.plist # Remove vmnetd binary echo "Removing com.docker.vmnetd binary..." sudo rm -f /Library/PrivilegedHelperTools/com.docker.vmnetd # Remove socket binary echo "Removing com.docker.socket binary..." sudo rm -f /Library/PrivilegedHelperTools/com.docker.socket # Install new binaries echo "Install new binaries..." sudo cp /Applications/Docker.app/Contents/Library/LaunchServices/com.docker.vmnetd /Library/PrivilegedHelperTools/ sudo cp /Applications/Docker.app/Contents/MacOS/com.docker.socket /Library/PrivilegedHelperTools/ 3. Restart Docker Desktop. 4. If this did not work, update to a newer version and rerun the steps (links here: https://docs.docker.com/desktop/release-notes/) More details in this issue: https://github.com/docker/for-mac/issues/7527

January 8, 2025 10:41 PST
January 8, 2025 18:41 UTC
[Identified] The root cause has been identified: some files in existing installations are incorrectly signed which can be fixed by copying correctly signed files from the Docker.app application bundle. We are working on a proper fix.

January 9, 2025 23:32 PST
January 10, 2025 07:32 UTC
[Monitoring] Patch releases for Docker Desktop versions 4.32 to 4.37 are now available. Please refer to https://docs.docker.com/desktop/cert-revoke-solution/ for more detail. We continue to monitor this situation.

January 13, 2025 07:21 PST
January 13, 2025 15:21 UTC
[Monitoring] We continue to work with our customers and users through the steps described in https://docs.docker.com/desktop/cert-revoke-solution/. We have not identified any new issues but continue to monitor the situation.
The official status page for services offered by Docker.

Docker Hub Registry

Operational

Docker Authentication

Operational

Docker Hub Web Services

Operational

Docker Desktop

Operational

Docker Billing

Operational

Docker Package Repositories

Operational

Docker Hub Automated Builds

Operational

Docker Hub Security Scanning

Operational

Docker Docs

Operational

Docker Community Forums

Operational

Docker Support

Operational

Docker.com Website

Operational

Docker Scout

Operational

Docker Build Cloud

Operational

Docker Registry Hub API Response Time

494.44ms




Docker Registry Hub API Uptime

100.00%




Docker Registry Response Time

487.08ms




Docker Registry Uptime

100.00%




Docker Com Response Time

482.68ms




Docker Com Uptime

100.00%




Docker Registry Hub API Response Time

480.38ms




Docker Registry Hub API Uptime

100.00%




Docker Registry Response Time

469.38ms




Docker Registry Uptime

100.00%




Docker Com Response Time

463.38ms




Docker Com Uptime

99.99%




Docker Registry Hub API Response Time

474.68ms




Docker Registry Hub API Uptime

100.00%




Docker Registry Response Time

470.55ms




Docker Registry Uptime

100.00%




Docker Com Response Time

439.19ms




Docker Com Uptime

99.99%