updating Time Machine setup: signal: killed

[david0]

Description

On my company managed device Time Machine is blocked.

After updating to the recent docker desktop version, startup fails with

Process Time Machine Syncing has exited Process Time Machine Syncing has exited. Select Restart to try running this process again, or, Ignore to continue without its functionality in Docker Desktop updating Time Machine setup: signal: killed

The docker desktop icon does not appear, even after restarting.

After killing all docker processes, somehow starting it works....

Reproduce

I guess an managed device where time machine is blocked is needed to re

Expected behavior

No response

docker version

Client:
 Version:           26.1.4
 API version:       1.45
 Go version:        go1.21.11
 Git commit:        5650f9b
 Built:             Wed Jun  5 11:26:02 2024
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.31.0 (153195)
 Engine:
  Version:          26.1.4
  API version:      1.45 (minimum version 1.24)
  Go version:       go1.21.11
  Git commit:       de5c9cf
  Built:            Wed Jun  5 11:29:12 2024
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.6.33
  GitCommit:        d2d58213f83a351ca8f528a95fbd145f5654e957
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client:
 Version:    26.1.4
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.14.1-desktop.1
    Path:     /Users/ottodavid/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.27.1-desktop.1
    Path:     /Users/ottodavid/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.32
    Path:     /Users/ottodavid/.docker/cli-plugins/docker-debug
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /Users/ottodavid/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.24
    Path:     /Users/ottodavid/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     /Users/ottodavid/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.2.0
    Path:     /Users/ottodavid/.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/ottodavid/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.9.3
    Path:     /Users/ottodavid/.docker/cli-plugins/docker-scout

Server:
 Containers: 12
  Running: 1
  Paused: 0
  Stopped: 11
 Images: 77
 Server Version: 26.1.4
 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: d2d58213f83a351ca8f528a95fbd145f5654e957
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
 Kernel Version: 6.6.31-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 11
 Total Memory: 7.657GiB
 Name: docker-desktop
 ID: 53a6ec5e-0c42-4d4a-a04e-dbe63f83f595
 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/xx/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

Diagnostics ID

0E3F8B91-D0B7-4FE3-9D0D-B315C61FA52F/20240701143552

Additional Info

No response

[pdrd]

Experiencing the same issue as described by @david0 on a company-managed MacBook with disabled Time Machine.

A click on Restart results in the same error dialog. A click on Continue allows successful startup of docker desktop and i have not experienced any malfunction. (As i am obviously not using any Time Machine-related features)

[thomo]

Same problem here, but

• click on Restart brings up the same error dialog again (and again)
• click on Continue starts docker but the desktop is not shown/accessible via menu bar

[donnie-coleman]

Still a problem in 4.37.2

[lukep-coxauto]

Still happening with 4.38.0

[karman-docker]

@lukep-coxauto If you click "Continue", is Docker Desktop starting fine ? If not, can you upload a diagnostic bundle and share its id please.

[lukep-coxauto]

Yes, all functionality I use works fine after hitting Continue. The modal comes back up every time I launch Docker.

[karman-docker]

Thanks for the confirmation @lukep-coxauto. We are working on suppressing that modal and logging a warning in the log file

[chaomonica]

@david0 @lukep-coxauto The fix will be included in the next Docker Desktop release (version 4.40). Please do let us know if the same issue is experienced in the new release.

[david0]

Thanks, now it starts without the "Process Time Machine Syncing has exited" dialog appearing!

Still this dialog is shown

The dialog is caused by Workspace ONE Intelligent Hub (VMWare) and is raised on every run of tmutil.

It would be nice if that dialog could be suppressed somehow too, but I guess Apple or VMWare would need to offer an API to check if TimeMachine backups are supported in advance.

Btw, this sounds related: https://github.com/rancher-sandbox/rancher-desktop/issues/1337