Skip to content

Docker Desktop 4.93.0 exits immediately on launch on macOS 26.6.2 (Apple Silicon) #725

Open

Description

@Macchiatobin

Bug report

Bug description

Docker Desktop 4.93.0 (240920), downloaded from the official Docker website for Apple Silicon and installed at /Applications/Docker.app, exits immediately when launched. The initial setup / subscription agreement screen never appears, and no Docker backend process remains running. Restarting the Mac did not resolve the issue.

Expected: Docker Desktop opens the initial setup screen and can start its engine after setup.
Actual: the app exits during launch before setup is displayed.

Reproduction steps

  1. Download the Apple Silicon Docker Desktop DMG from the official website.
  2. Copy Docker.app to Applications.
  3. Launch /Applications/Docker.app from Finder or with open /Applications/Docker.app.
  4. Observe the immediate exit, with no setup screen.
  5. Restart macOS and retry: the same behavior occurs.

Observed errors

The macOS launch attempt reports:

RBSRequestErrorDomain Code=5: Launched process exited during launch.

Running com.docker.backend --help directly also exits with status 137. Around the failed launch, system logs include:

taskgated-helper: com.docker.docker: Unsatisfied entitlements: com.apple.security.application-groups
taskgated-helper: Disallowing: com.docker.docker
amfid: Soft-restriction provisioning profile validation failure:
AppleMobileFileIntegrityError Code=-413 "No matching profile found"

Checks performed

  • The backend is a native arm64 executable.
  • codesign --verify --deep --strict /Applications/Docker.app passes.
  • spctl --assess --type execute --verbose /Applications/Docker.app reports accepted, source Notarized Developer ID.
  • The backend is signed by Docker Inc (Team ID 9BNSXJN65R).
  • The backend claims com.apple.security.application-groups = [group.com.docker], but the embedded provisioning profile does not include that entitlement. The profile expires in October 2043, so it is not expired.
  • SHA-256 comparison confirms the installed backend and embedded provisioning profile are byte-for-byte identical to those in the downloaded DMG.
  • No app re-signing, macOS security changes, or downgrade has been attempted.

The entitlement messages are observations, not a confirmed root cause: Apple's documentation notes that an unvalidated app-group entitlement alone does not necessarily terminate a macOS process. Could you help identify the cause of this immediate exit and a supported workaround?

Diagnostics

A bundle was collected locally using com.docker.diagnose gather, without -upload. The attached archive is an intentionally reduced / redacted version: device identifiers, network snapshots, unrelated process inventories, and unrelated system logs were removed. Docker launch errors and relevant version information are retained. If any removed information is further needed for diagnosis pls lmk.

docker-startup-diagnostics-redacted.zip

Platform

macOS

Version information

Docker Desktop: 4.93.0 (240920), main channel
macOS: 26.6.2 (25G83)
Architecture: arm64 (Apple Silicon)
Hardware: MacBook Pro, Apple M2 Pro, 16 GB RAM

Bundled versions reported by the diagnostics tool (engine not running):
Engine: 29.8.1
Buildx: v0.37.1
Compose: v5.5.1

The backend cannot start, so live client/server version output is unavailable.

Diagnostics ID

No response

Activity

  1. added theissue type on Oct 4, 2026
  2. voonyee commented on Oct 5, 2026

    @voonyee
    Collaborator

    Hi, thanks for reporting this.

    Can you:

    1. Run the following in Terminal and paste the output:
      Try to open Docker once, then run log show --last 5m --style syslog --predicate 'process == "kernel" OR process == "syspolicyd" OR process == "amfid"' | grep -i -E 'docker|killing|code signature|AppleSystemPolicy' codesign -d --entitlements :- /Applications/Docker.app/Contents/MacOS/com.docker.backend profiles status -type enrollment

    2. Is this Mac managed by your employer (device management or a corporate VPN client)? If yes, does Docker Desktop launch from a different, unmanaged user account or Mac?

    3. Does an earlier Docker Desktop version, open on the same Mac?

    4. If you're comfortable with it, you can also try adding Docker to System Settings → Privacy & Security → Full Disk Access and relaunching. Please only do this if your IT policy allows it, and tell us whether it changes anything.

  3. Macchiatobin commented on Oct 5, 2026

    @Macchiatobin
    Author
    1. Output for 3 commands:
    macchiato@Macchiatoui-MacBookPro ~ % log show --last 5m --style syslog --predicate 'process == "kernel" OR process == "syspolicyd" OR process == "amfid"' | grep -i -E 'docker|killing|code signature|AppleSystemPolicy'
    macchiato@Macchiatoui-MacBookPro ~ % codesign -d --entitlements :- /Applications/Docker.app/Contents/MacOS/com.docker.backend
    Executable=/Applications/Docker.app/Contents/MacOS/com.docker.backend
    warning: Specifying ':' in the path is deprecated and will not work in a future release
    <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "https://www.apple.com/DTDs/PropertyList-1.0.dtd"><plist version="1.0"><dict><key>com.apple.security.app-sandbox</key><false/><key>com.apple.security.application-groups</key><array><string>group.com.docker</string></array><key>com.apple.security.automation.apple-events</key><true/><key>com.apple.security.cs.allow-unsigned-executable-memory</key><true/><key>com.apple.security.hypervisor</key><true/><key>com.apple.security.virtualization</key><true/><key>keychain-access-groups</key><array><string>9BNSXJN65R.com.docker.pass.shared</string></array></dict></plist>
    macchiato@Macchiatoui-MacBookPro ~ % profiles status -type enrollment
    Enrolled via DEP: No
    MDM enrollment: No
    
    1. To the best of my knowledge, the answer is No.
    2. I tried 4.92.0 and same issue occurs.
    3. I did the setting changes and no change was observed.
  4. voonyee commented on Oct 6, 2026

    @voonyee
    Collaborator

    Thanks for providing the output.

    So far, still unclear what might be causing it. Can you try a clean uninstall of Docker Desktop, install Docker Desktop to see if the issue persists?

    1. Clean uninstall of Docker Desktop following this link: https://docs.docker.com/desktop/uninstall/
      Please remember to do the following:

    After uninstalling Docker Desktop, some residual files may remain which you can remove:
    rm -rf ~/Library/Group\ Containers/group.com.docker
    rm -rf ~/.docker

    1. Let's install the latest Docker Desktop (4.94), you can get it from release notes: https://docs.docker.com/desktop/release-notes/

    If issue persists, can you generate a new Diagnostics log and share with us the Diagnostics ID?
    https://docs.docker.com/desktop/troubleshoot-and-support/troubleshoot/#diagnose-from-the-terminal

    /Applications/Docker.app/Contents/MacOS/com.docker.diagnose gather -upload

    You shared that running Running com.docker.backend --help directly also exits with status 137. Can you check under macOS setting for "Privacy & Security", any restriction from starting Docker Desktop? If you have any security software, can temporary disable it to see if it helps?

  5. Macchiatobin commented on Oct 6, 2026

    @Macchiatobin
    Author

    Hi, I just uninstalled docker following the official instruction and re-installed it. (I just did it using ver 4.92 I previously downloaded)
    And the issue persists.

    Thus I uploaded the diagnostics log and the ID is BDD76848-15BB-4276-94A4-C1AB18FE61BB/20261006043044.

    And I double-checked my macOS's privacy & security setting and no potentially problematic setting (at least to me) was located.

    Thank you.

  6. voonyee commented on Oct 6, 2026

    @voonyee
    Collaborator

    Thanks for trying that. So far, it seems that Docker Desktop shutdown at the moment it starts, before Docker itself runs.

    I am still unsure what is causing that. Try to open Docker once, then immediately run:

    1. log show --last 5m --style syslog --predicate 'process == "kernel" OR process == "syspolicyd" OR process == "amfid"' | grep -i -E 'docker|killing|code signature|AppleSystemPolicy'
    2. codesign -d --entitlements :- /Applications/Docker.app/Contents/MacOS/com.docker.backend profiles status -type enrollment

    Earlier, the output of command 1 returns nothing. Let's see if you open Docker and run it immediately, does it return any output?

    • In the latest bundle, it shows a VPN that is connected for 8 days. If there is a VPN connected, can you try to disconnect it and see if the issue persists?
    • If this is possible, can you try with a different local user account, is the issue persists?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions