Skip to content

Docker desktop stops - Process has exited error #13896

Closed

Description

@tamas-pim

Description

After 10 minutes docker desktop dies, with the error: "Process has exited". It happened after i updated to the latest docker desktop version on WIN.
image

Reproduce

I can't reproduce it, it just dies after 10-15 minutes.

Expected behavior

Docker desktop should not die and quit

docker version

Client:
 Cloud integration: v1.0.35+desktop.10
 Version:           25.0.1
 API version:       1.44
 Go version:        go1.21.6
 Git commit:        29cf629
 Built:             Tue Jan 23 23:10:35 2024
 OS/Arch:           windows/amd64
 Context:           default

Server: Docker Desktop 4.27.0 (135262)
 Engine:
  Version:          25.0.1
  API version:      1.44 (minimum version 1.24)
  Go version:       go1.21.6
  Git commit:       71fa3ab
  Built:            Tue Jan 23 23:09:46 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.27
  GitCommit:        a1496014c916f9e62104b33d1bb5bd03b0858e59
 runc:
  Version:          1.1.11
  GitCommit:        v1.1.11-0-g4bccb38
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client:
 Version:    25.0.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.12.1-desktop.4
    Path:     C:\Program Files\Docker\cli-plugins\docker-buildx.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.24.3-desktop.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-compose.exe
  debug: Get a shell into any image or container. (Docker Inc.)
    Version:  0.0.22
    Path:     C:\Program Files\Docker\cli-plugins\docker-debug.exe
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-dev.exe
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.21
    Path:     C:\Program Files\Docker\cli-plugins\docker-extension.exe
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.4
    Path:     C:\Program Files\Docker\cli-plugins\docker-feedback.exe
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.0.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-init.exe
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-sbom.exe
  scout: Docker Scout (Docker Inc.)
    Version:  v1.3.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-scout.exe

Server:
 Containers: 9
  Running: 6
  Paused: 0
  Stopped: 3
 Images: 15
 Server Version: 25.0.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: a1496014c916f9e62104b33d1bb5bd03b0858e59
 runc version: v1.1.11-0-g4bccb38
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
 Kernel Version: 5.15.133.1-microsoft-standard-WSL2
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 16
 Total Memory: 15.33GiB
 Name: docker-desktop
 ID: f67409bc-d7d4-44e3-8456-4f1ecb283950
 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
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: daemon is not using the default seccomp profile

Diagnostics ID

B5B3D3AD-FEDD-4170-98EF-28A6CF92BF09/20240131131216

Additional Info

No response

Activity

  1. bsousaa commented on Feb 1, 2024

    @bsousaa
    Contributor

    The self-diagnose is showing:

    Failed with: [ 4.165319] EXT4-fs error (device sdc): ext4_put_super:1196: comm weston: Couldn't clean up the journalIf the WSL 2 Linux filesystem is corrupt then Docker Desktop cannot start.There is a known issue fixed in Windows Insider builds which can cause filesystem corruption, see:microsoft/WSL#5895 .Try running "wsl --shutdown" to stop your WSL Virtual Machine. When it restarts it willrun a filesystem check and hopefully fix the problem.

    you may restart your WSL vm and try again wsl --shutdown

  2. MihaelaStoica commented on Feb 2, 2024

    @MihaelaStoica

    This is the same issue as #13885 and #13899. We are working on a fix, to be included in the next Docker Desktop release.

  3. alper-guven commented on Feb 6, 2024

    @alper-guven

    4.27.1 was keep crashing after 15 minutes or immediately if I go to Settings > Kubernetes tab.

    Downgrading from 4.27.1 to 4.26.1 fixed the crashing issue.

    Downgrading is not the best solution but at least i can work without being interrupted every 15 minutes.

    You can follow the directions here to downgrade:
    https://stackoverflow.com/a/77224786/6835017

  4. MihaelaStoica commented on Feb 9, 2024

    @MihaelaStoica

    Docker Desktop 4.27.2 includes a fix for this issue (see release notes), thanks everyone for your patience while we worked on this fix.

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

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions