Container operations

Container services expose operational tools in the service drawer. DockDash sends each request back to the Docker daemon or Kubernetes cluster from which the service was discovered.

Privileged access

Container controls, terminals, and file editing can provide host- or cluster-level access. Protect DockDash with authentication, grant only the runtime permissions you need, and disable unused capabilities.

See Security for deployment boundaries and feature controls for the disable switches.

Runtime controls

Docker containers can be started, stopped, and restarted. Kubernetes works at the workload-controller level: DockDash can recreate a pod managed by a controller, but it does not start or stop individual Kubernetes containers.

Logs

DockDash streams recent and live container output in the browser. It normalizes timestamps and terminal color sequences so Docker and Kubernetes logs remain readable in the same interface.

Terminal access

The terminal opens an interactive shell inside the selected container. DockDash tries Bash when it is installed and falls back to sh.

Terminal sessions are tied to the signed-in browser session and are closed when the connection ends. They still carry the permissions of the process inside the container.

File access

The file explorer lists directories and reads or writes text files inside Docker and Kubernetes containers. Whether an operation succeeds depends on the tools, filesystem, and permissions available inside that container.