[madhavkhoslaa]

What is this?

Docker on the QS Bar: a whale glyph with the running-container count, and a panel to

• start / stop the Docker daemon and toggle start-at-boot,
• list every container with start / stop / restart (a spinner while it works),
• click a container to edit its published ports and mounts; APPLY recreates it from its own inspect data (same image ID, env, networks, labels) with automatic rollback if the new one fails. Volumes are never deleted.

Privileged actions: the first daemon click (or the panel's ALLOW banner) runs pkexec bin/docker-ctl-setup install once. That installs a root-owned helper at /usr/local/libexec/docker-ctl-daemon that accepts only start|stop|enable|disable and calls ryoku-host svc --system for docker.service/docker.socket, plus a polkit action letting the active local session run it without a password (inactive/remote sessions still need admin auth). docker-ctl-setup uninstall removes both. The README documents every command.

Container control uses the Engine API over /var/run/docker.sock (Python stdlib, no network). Service queries go through ryoku-host svc, so there is no direct systemctl.

Checklist

• One folder under its catalogue with a manifest and a real preview image (not a placeholder).
• One entry added to that catalogue's registry.json (lastUpdated in YYYY-MM-DD; official: false for community items).
• Tested live in Ryoku, it renders and behaves correctly (installed with ryoku plugin add).
• tests/validate-catalogue.sh passes from the repo root.
• I own or have permission to submit this content, and it is licensed for redistribution.
• It does not overwrite user configuration or run privileged commands without clear consent.

Opened with ryoku plugin share; the product manifest and the registry entry were generated from the installed plugin.

[neur0map]

Thanks for this, Docker is live in the store now with a small fix on top so it only uses the Docker access you already have instead of asking for root.