Prove SSH and Docker access first
From the same remote account, verify SSH authentication and Docker access. If that account cannot reach the Docker Engine, the UI cannot grant that permission for it. Use a trusted operator account rather than exposing an unauthenticated Engine endpoint.
Open the host's Docker workspace
Confirm the host identity and inspect the overview. Choose a container and inspect status and logs before deciding which operation is needed. Distinguish a stopped container from a host connection failure.
Choose the correct operating context
Use the host terminal for host-level commands, and the container terminal for a supported exec session inside a container. Validate Compose configuration before deployment. Review destructive confirmation text and the affected resource carefully.
Check the service after the action
Return to the container view and logs, then verify the application through its normal endpoint. Console Hub's lifecycle controls do not replace application health checks, change management or backups.