Docker Manager drives the local Docker daemon from the panel: containers, images, volumes, networks and Compose stacks. The panel process is unprivileged and cannot open the Docker socket, so every socket-touching command is routed through the root VinzaPanel agent; a local subprocess is used only as a fallback when the agent is unreachable and the panel happens to have socket access, while cheap probes such as the Docker version and whether the service is active run locally so the sidebar and dashboard stay responsive.

Containers can be listed, started, stopped, restarted and removed, created from an image with ports, environment variables, volumes, a restart policy and a command, edited and recreated in place, inspected, tailed with follow, and watched through auto-refreshing stats. There is a browser terminal that opens a real interactive session inside a running container over a WebSocket to a PTY handler in the agent, so programs like top and vi work; the older one-shot exec console remains as a programmatic fallback. Images can be pulled, built from an inline Dockerfile and removed, and the system view shows disk usage and can prune. Pulls, builds, runs, Compose deploys and prunes run as background jobs on the server, so they are not cut off after half a minute and keep going if the page is closed; the page follows their output. Edit & recreate validates the new settings first, carries over every volume, the host IP and protocol of each port and the networks, and puts the old container back if the new one does not start.

Compose stacks are stored panel-side under /opt/vinza/compose and can be deployed from an inline docker-compose.yml then brought up, down, restarted, pulled, listed and tailed. Several things are refused on purpose rather than merely discouraged: bind mounts of the root filesystem, /root, /etc (except a read-only /etc/localtime or /etc/timezone), /proc, /sys, /dev, /boot, /run (where the Docker socket lives) and Docker's own data, in both the run form and Compose files; privileged mode, host pid/ipc/user namespaces, host devices and dangerous capabilities in Compose files; and removal of the built-in bridge, host and none networks. Container names, image references, port mappings and environment keys are validated against Docker's own character sets before anything reaches the agent's shell. The plugin manages the node it runs on. It installs Docker from Docker's official repository when that repository supports the release, otherwise from the distribution's packages, and uninstalling the app removes Docker only if the app installed it; the interactive terminal is admin-only and local-node only.

Availability: Included at no extra cost with the Profesional and Enterprise plans. On the Free and Starter plans it is available per server as a monthly subscription ($4.99/month) or a one-time purchase ($49).

Min Panel Version

1.0.0

Platform

Ubuntu 20.04+ / 22.04+ / 24.04+

License

Paid license required

Permissions

websites.manage

VinzaPanel handles installation automatically via the Vinza Store. Make sure the panel agent has internet access to download dependencies.

1.2.5 — Domain + SSL for a container: map a domain to a port the container publishes; the panel creates a Custom App / Proxy website forwarding to it and can issue a Let's Encrypt certificate. Private registries: log in (the password reaches docker login on stdin from a root-only file, never a command line), list and log out. App templates: one-click Uptime Kuma, n8n, Adminer, MinIO and Redis as compose stacks, with port checks and generated passwords shown once (Portainer is left out: it needs the Docker socket, which the compose policy refuses). CPU and memory limits (--cpus, --memory) when running or editing a container, validated and kept on recreate. 1.2.4 — Security: names shown in the page (from the server, its sites or its users) are passed to buttons safely; a quote in one could run script in the admin's browser. 1.2.3 — Long operations (run, pull, build, recreate, Compose deploy/actions, prune) finish in the UI again: the progress check they poll (job_status) was missing from the plugin's action list, so every one of them failed with "Action not available" while the job carried on in the background. 1.2.2 — Background jobs started through systemd now get their script intact: systemd rewrote `$` on the command line, which broke recreate, build and other multi-step jobs on servers with systemd. 1.2.1 — Long operations (pull, build, run, recreate, Compose deploy/actions, prune) run as background jobs instead of being killed after 30 seconds. Edit & recreate no longer deletes the container before checking the new settings, keeps anonymous volumes, port host IPs/protocols and networks, does not pin the image's own environment, and restores the old container if the new one fails; containers of a Compose stack are edited through the stack. Install falls back to the distribution's Docker when Docker's repository lacks the release (a dead repo line used to break apt for the whole server) and adds the compose plugin to an existing Docker; uninstall removes Docker only if the app installed it. Compose: stacks deployed elsewhere can be stopped/restarted, files are deleted only after `down` worked, project names follow compose's rules. Volume/network names with uppercase or dots work. Bind-mount checks normalise paths and also cover /run and Compose files. 1.2.0 — Interactive terminal: a real `docker exec -it` TTY in the browser (xterm.js over WebSocket → new agent `docker.exec_stream` PTY handler). top, vi, and interactive prompts now work — superseding the 1.1.0 one-shot exec console (still available as a programmatic fallback). Admin-only, local node. 1.1.0 — Compose stacks (deploy/up/down/restart/pull/logs from an inline docker-compose.yml, panel-managed under /opt/vinza/compose; socket-mount and privileged mode refused). Volumes tab (create/remove/prune). Networks tab (create/remove built-in-protected, driver picker). Exec console — run one command at a time inside a running container via docker exec (with shell picker + command history); note it is NOT a live TTY, so interactive programs like top/vi are out of scope (a full PTY terminal is a planned follow-up). Live-follow container & compose logs (2s polling) and auto-refreshing Live stats. Edit & recreate a container (change ports/env/volumes/restart/command in place). 1.0.0 — Initial release: container lifecycle, image pull/build, logs, inspect, one-shot stats, prune, disk usage.

Use VinzaPanel's REST API to download and install this app programmatically.

Download app files

HTTP

POST /plugins/api/download/docker-manager/
Content-Type: application/json

{
  "panel_version": "1.0.0"
}

Example response

JSON

{
  "success": true,
  "plugin_id": "docker-manager",
  "version": "1.2.5",
  "download_url": "..."
}