Portainer
Portainer: a first setup, important settings, verification, and recovery considerations.
Working directory: ~/homelab/ops/container-management. Follow the common setup workflow first. This is a setup note based on the linked documentation, not a copy of my live configuration or a runtime verification of this full stack.
Start here
Portainer provides a Docker management interface. It is optional; the introductory Compose workflow works without it. Follow the official local-Docker installation on a practice host only after understanding that Docker management commonly grants control equivalent to root on that host.
Settings and data
Persist Portainer's /data and complete initial administrator setup promptly through private access. Review whether you need local socket access or a supported agent. A socket mounted read-only does not make Docker API operations read-only. Keep the management interface off public routes.
Check it
Confirm that the UI shows the intended practice endpoint and only then inspect a disposable container. Decide whether a stack is managed from Git/Compose or through the UI. Avoid making competing edits in both places because the next redeployment can overwrite one side.
When something fails
An unreachable endpoint needs socket/agent connectivity and permissions checked, not wider internet exposure. A missing stack may be a different Docker endpoint or project. Back up Portainer state, but remember that its backup does not automatically contain every managed application's database or files.