Docker Desktop starts a new instance of Waybar for showing the tray icon
Description
I run Docker Desktop on Ubuntu 23.04 with Sway and waybar. Waybar is started in sway config with minimal default setup: bar { swaybar_command waybar }
Waybar config contains default tray module "tray": { "icon-size": 22, "spacing":13 },
When starting the docker desktop I get the docker icon on the tray module in the waybar ( as expected ) but a new instance of waybar on top of the existing. The icon is otherwise clickable and working. The only issue is that I have two instances of the waybar.
sway version: 1.7 Waybar version: v0.9.17 Docker desktop version: 4.23.0
Reproduce
Start Docker Desktop on a system with the Sway windows manager and Waybar.
Expected behavior
It shouldn't start a second instance of Waybar.
docker version
Client: Docker Engine - Community
Cloud integration: v1.0.35+desktop.4
Version: 24.0.6
API version: 1.43
Go version: go1.20.7
Git commit: ed223bc
Built: Mon Sep 4 12:31:40 2023
OS/Arch: linux/amd64
Context: desktop-linux
Server: Docker Desktop 4.23.0 (120376)
Engine:
Version: 24.0.6
API version: 1.43 (minimum version 1.12)
Go version: go1.20.7
Git commit: 1a79695
Built: Mon Sep 4 12:32:16 2023
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.22
GitCommit: 8165feabfdfe38c65b599c4993d227328c231fca
runc:
Version: 1.1.8
GitCommit: v1.1.8-0-g82f18fe
docker-init:
Version: 0.19.0
GitCommit: de40ad0
docker info
Client: Docker Engine - Community
Version: 24.0.6
Context: desktop-linux
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.11.2-desktop.4
Path: /usr/lib/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.21.0-desktop.1
Path: /usr/lib/docker/cli-plugins/docker-compose
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.0
Path: /usr/lib/docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.20
Path: /usr/lib/docker/cli-plugins/docker-extension
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v0.1.0-beta.7
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
scan: Docker Scan (Docker Inc.)
Version: v0.26.0
Path: /usr/lib/docker/cli-plugins/docker-scan
scout: Command line tool for Docker Scout (Docker Inc.)
Version: 0.24.1
Path: /usr/lib/docker/cli-plugins/docker-scout
Server:
Containers: 5
Running: 0
Paused: 0
Stopped: 5
Images: 8
Server Version: 24.0.6
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: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 8165feabfdfe38c65b599c4993d227328c231fca
runc version: v1.1.8-0-g82f18fe
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
cgroupns
Kernel Version: 6.3.13-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 7.424GiB
Name: docker-desktop
ID: 6933e35a-797a-4339-a07f-4baca624c517
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: daemon is not using the default seccomp profile
Diagnostics ID
302cb22d-508b-4766-8739-ef4a0d7d78dc/20230919223117
Additional Info
No response
Same issue on upgraded Ubuntu 23.10 with versions: └>$ sway --version sway version 1.8.1 └>$ waybar --version Waybar v0.9.22 and Docker Desktop 4.24.2
Same exact issue. Fedora version: Fedora release 39 (Thirty Nine) Kernel version: 6.7.3-200.fc39.x86_64 Waybar version: Waybar v0.9.24
Same issue Ubuntu 22.04, waybar version v0.9.9, and sway version 1.7
Did you guys find any workarounds
Not really. I just have a dummy alias of killing waybars and restarting sway that I run in a terminal. alias fix_waybar='sudo killall waybar; swaymsg reload'