Workflow · Native macOS # Work with remote Docker containers through SSH. Termy brings remote Docker inspection, logs, exec sessions and lifecycle actions into a native macOS workspace. Access the host over SSH and keep container operations next to the host’s terminal and diagnostics. Docker and other production integrations are part of the Pro workspace. By [Termy](https://termyapp.com/about) · Updated 6 September 2026 [Download for macOS](https://dl.termyapp.com/releases/Termy-1.7.9.dmg)[Compare Free and Pro ↗](https://termyapp.com/pricing) Transport **Through an SSH-accessible host** Container work **Inspection, logs, exec and lifecycle actions** Related integrations **Kubernetes and Nomad** Platform **macOS 26 or later** Access requirement **The host account must have the required container permissions**  A real Termy workspace. Available features depend on the selected plan. ## Start with a working host connection Connect to the machine that owns the Docker workload and verify the SSH account’s access. Termy uses the host you already trust for the remote workflow, so you do not need to expose another public management endpoint solely for this path. SSH reachability and Docker authorization are separate. If a shell connects but container inspection fails, check the remote account’s Docker permissions and the availability of the container runtime on that machine. ## Move from a symptom to the right container Use Host X-ray to look at the machine as a whole: pressure on memory or disks, running processes, ports and services. Then inspect the relevant container, review logs and open an exec session when the task requires one. This order matters when multiple services share a host. Restarting the container may not resolve a full disk or host-wide resource pressure. Keeping the host and container views together helps preserve that context. - Confirm the host and environment. - Inspect host pressure and the affected workload. - Read container logs before making a lifecycle change. - Use exec only with the permissions and scope the task needs. ## Review a change before applying it Termy’s Safe Actions present the target, intended command or API request, risk, verification and rollback information before an operation runs. Read the scope carefully for a lifecycle change that can interrupt service. For repeated work across hosts, Broadcast and Pipelines add canaries, concurrency limits, pause and resume, stop-on-error and per-host results. Validate the result on the first host before expanding a rollout. ## Choose the correct integration Docker, Kubernetes and Nomad are separate integration paths. A Docker host connection should not be treated as a substitute for access to a Kubernetes cluster or Nomad environment. Termy is an operations client. It does not replace your deployment system, runtime authorization or service-specific recovery procedure. Consult the compatibility page for documented maturity and supported platform requirements. ## Common questions ### Can I inspect Docker containers from my Mac over SSH? Yes. Termy Pro provides remote container inspection, streaming logs, exec sessions and lifecycle actions through an SSH-accessible host. ### Does SSH access automatically grant Docker permissions? No. The remote account must also have permission to perform the requested Docker operation. ### Does Termy also support Kubernetes and Nomad? Yes, both are listed integrations in Termy’s production workspace. They use their own connection and authorization context. ## Keep exploring - [Native SSH Client for macOS](https://termyapp.com/ssh-client-macos) - [Supported Playbooks behavior](https://termyapp.com/automation-compatibility) - [Platform and integration compatibility](https://termyapp.com/compatibility) --- Official source: [Manage Docker over SSH from Mac — Termy](https://termyapp.com/docker-over-ssh)