27 lines
1.2 KiB
Markdown
27 lines
1.2 KiB
Markdown
# Portainer Agent
|
|
|
|
Lightweight Portainer remote agent that allows a Portainer server instance to manage this Pi's Docker remotely.
|
|
|
|
## Access
|
|
- **Port:** `9001` (TCP) — Portainer server connects to this
|
|
|
|
## Containers
|
|
|
|
| Container | Image | Role |
|
|
|---|---|---|
|
|
| `portainer_agent` | `portainer/agent:latest` | Remote Docker management agent |
|
|
|
|
## Compose File
|
|
**Path:** `/home/artanis/Desktop/Portainer_Agent/docker-compose.yml` (on the Pi)
|
|
|
|
> Dockhand reports the compose location as unknown (`needsFileLocation: true`). Path inferred from container labels.
|
|
|
|
Compose content not available via API. Key details from container labels and mounts:
|
|
- Mounts `/var/lib/docker/volumes` and `/var/run/docker.sock` into the agent container
|
|
- Exposes port `9001` on all interfaces
|
|
|
|
## Notes
|
|
- No Portainer server is currently running in Docker on either the homelab or this Pi (the `portainer` stack on the homelab has no containers and is in `created` state)
|
|
- This agent is likely a leftover from a previous setup, or is intended to connect to a Portainer server instance not yet deployed
|
|
- The agent has full access to the Pi's Docker socket and volumes — it should only be reachable by a trusted Portainer server
|