Docker desktop logs out daily unexpectedly and stops all containers

[fewebahr]

Description

Docker desktop for Mac M3 Pro running MacOS Sonoma 14.7 logs out from Docker almost every day, and stops all running containers. Current version is 4.35.1, but this problem impacted prior versions as well.

Reproduce

Install Docker Desktop for Mac (possibly on one of the same spec) and then use for a few days, then logouts occur regularly.

Expected behavior

Docker desktop stays logged in for weeks or months, or better yet a configurable period.

docker version

Client:
 Version:           27.3.1
 API version:       1.47
 Go version:        go1.22.7
 Git commit:        ce12230
 Built:             Fri Sep 20 11:38:18 2024
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.35.1 (173168)
 Engine:
  Version:          27.3.1
  API version:      1.47 (minimum version 1.24)
  Go version:       go1.22.7
  Git commit:       41ca978
  Built:            Fri Sep 20 11:41:19 2024
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.7.21
  GitCommit:        472731909fa34bd7bc9c087e4c27943f9835f111
 runc:
  Version:          1.1.13
  GitCommit:        v1.1.13-0-g58aa920
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client:
 Version:    27.3.1
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.17.1-desktop.1
    Path:     /Users/gellis/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.7-desktop.1
    Path:     /Users/gellis/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.37
    Path:     /Users/gellis/.docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Alpha) (Docker Inc.)
    Version:  v0.0.15
    Path:     /Users/gellis/.docker/cli-plugins/docker-desktop
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /Users/gellis/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.27
    Path:     /Users/gellis/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     /Users/gellis/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.3.0
    Path:     /Users/gellis/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/gellis/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.14.0
    Path:     /Users/gellis/.docker/cli-plugins/docker-scout

Server:
 Containers: 3
  Running: 3
  Paused: 0
  Stopped: 0
 Images: 11
 Server Version: 27.3.1
 Storage Driver: overlayfs
  driver-type: io.containerd.snapshotter.v1
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: runc io.containerd.runc.v2
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 472731909fa34bd7bc9c087e4c27943f9835f111
 runc version: v1.1.13-0-g58aa920
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.10.11-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 12
 Total Memory: 11.67GiB
 Name: docker-desktop
 ID: d1835cb0-16c0-4170-845f-c569afaeb5ba
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Labels:
  com.docker.desktop.address=unix:///Users/gellis/Library/Containers/com.docker.docker/Data/docker-cli.sock
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: daemon is not using the default seccomp profile

Diagnostics ID

N/A

Additional Info

No response

[jpbriend]

Hi @fewebahr ,
would you mind generating a Diagnostic and post the ID here so that I can have a look at what is happening?

[arturasmckwcz]

Hi @fewebahr , would you mind generating a Diagnostic and post the ID here so that I can have a look at what is happening?

I've run into a similar issue. I click "Sign in" get redirected to login page on Chrome. successfully login using Gmail and instantly get signed out.

And I can't provide diagnostics ID cos it doesn't generate anything, only "Docker Engine stopped"
Version info:
Version: 4.35.1 (173168)
Engine: 27.3.1
Compose: v2.29.7-desktop.1
Credential Helper: v0.8.2
Kubernetes: v1.30.2

PS I can login into the hub

[jpbriend]

@arturasmckwcz you can generate a diagnostic using the command line, even if the underlying engine is not started: https://docs.docker.com/desktop/troubleshoot-and-support/troubleshoot/#diagnose-from-the-terminal

[fewebahr]

Hey @jpbriend - thanks for your help! Here is my diagnostic ID:

0EBD3ACD-EB03-4EE1-AEB3-EFB112C214C9/20241119172232

[jpbriend]

@fewebahr according to the logs, the last time you got signed out is November 16th (around 9PM GMT) and it was because your token could not be renewed because Post "https://login.docker.com/oauth/token": unexpected EOF.
This looks like a network issue. The previous renewals (~ every hour) were successful (I can't read before November 15th, the previous logs are not in the diagnostic anymore).

Either it was an issue on login.docker.com side, either you have network disconnections on your side (net work disconnection could be a slow shutdown of your computer, and the wifi is stopped before Docker Desktop).

When you hit again this issue, can you regenerate a diagnostic and share it with me? Also, try to get as much details as you can regarding networking at that time: usage of proxy, wifi connectivity, mac status (maybe it's shutting down network when inactive), etc...
Many issues started to happen with MacOS 15 around networking, I would not be surprised some kind of "disable wifi when inactive" option has been added.