docker
Docker Desktop starts on login regardless of setting
Description
The setting "Start Docker Desktop when you sign in to your computer" is not having it's value respected, and the app is starting on login even when unchecked.
NOTE: This seems to be a reappearance of #2950
Reproduce
Re-login after disabling that setting
Expected behavior
"Start Docker Desktop when you sign in to your computer" being unchecked should not result in docker-desktop running at login.
docker version
Client: Docker Engine - Community
Cloud integration: v1.0.35+desktop.13
Version: 26.1.2
API version: 1.45
Go version: go1.21.10
Git commit: 211e74b
Built: Wed May 8 13:59:59 2024
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 26.1.2
API version: 1.45 (minimum version 1.24)
Go version: go1.21.10
Git commit: ef1912d
Built: Wed May 8 13:59:59 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.31
GitCommit: e377cd56a71523140ca6ae87e30244719194a521
runc:
Version: 1.1.12
GitCommit: v1.1.12-0-g51d5e94
docker-init:
Version: 0.19.0
GitCommit: de40ad0
### docker info
```bash
Client: Docker Engine - Community
Version: 26.1.2
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.14.0-desktop.1
Path: /usr/lib/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.27.0-desktop.2
Path: /usr/lib/docker/cli-plugins/docker-compose
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.29
Path: /usr/lib/docker/cli-plugins/docker-debug
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: /usr/lib/docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.23
Path: /usr/lib/docker/cli-plugins/docker-extension
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.4
Path: /usr/lib/docker/cli-plugins/docker-feedback
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.1.0
Path: /usr/lib/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: /usr/lib/docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.8.0
Path: /usr/lib/docker/cli-plugins/docker-scout
Server:
Containers: 10
Running: 2
Paused: 0
Stopped: 8
Images: 48
Server Version: 26.1.2
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: systemd
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: io.containerd.runc.v2 nvidia runc
Default Runtime: runc
Init Binary: docker-init
containerd version: e377cd56a71523140ca6ae87e30244719194a521
runc version: v1.1.12-0-g51d5e94
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.1.0-17-amd64
Operating System: Debian GNU/Linux 12 (bookworm)
OSType: linux
Architecture: x86_64
CPUs: 16
Total Memory: 31.25GiB
Name: debian
ID: 40e26dc9-f00e-4714-b450-a8ed07a2d998
Docker Root Dir: /var/lib/docker
Debug Mode: false
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
### Diagnostics ID
38AD7F19-CAA6-4B7D-970E-777A2427A147/20240510075805
### Additional Info
Output of `lsb_release -a`:
No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 12 (bookworm) Release: 12 Codename: bookworm
Same for me, though I could get the same effect by disabling the systemd service with systemctl --user disable docker-desktop.service
OS: EndeavorOS 6.13.2-arch1-1 App Version: 4.38.0-1 Steps to reproduce: Install Docker-Desktop following instructions from docker.com website.
EDIT: Additional detail, docker-descktop.service was not listed when using systemctl yet when using borgaar's suggested command, systemctl gave a positive response. Docker Desktop removed for displaying dangerous behavior.
Yep, still going on. Used systemctl on various docker services, etc... nothign was working. Docker Desktop mysteriously quit without user intervention after one of many, many restarts and now did not come back.
Just to be sure, I issued borgaar's suggestion and even though docker-desktop.service was never listed when grepping services? Systemctl issued a response confirming disabling the process. Which is odd since it was never listed as a process in the first place when using systemctl to list processes.
