Your containers, through Portainer.
Tillarr reaches Docker through Portainer rather than the Docker socket, so it never needs root on your host. The first beta watches Portainer; during the beta it shows your containers and lets you restart them.
What you see
- Whether it answers, how quickly, and which address answered
- Its version, read without a key
- A tap to open its own web page
What's next
During the beta: environments, containers with their state and health, and stacks. Start, stop or restart a container after a confirmation.
Connect Portainer
What to have ready when you add it in Tillarr.
- Its address. Usually https://your-server:9443. Add a remote address too, and Tillarr uses it when home doesn't answer.
- Nothing else. Watching needs no key and no login, so it's free and can't change anything in Portainer. When full support arrives, Tillarr asks for its key.
Good to know
- Portainer refuses its API key when another Authorization header comes with it, which breaks behind some sign-in proxies.
- Portainer uses its own certificate on port 9443, so trust its fingerprint once.
- Image update status is in Portainer's Business Edition only.
Behind a sign-in page
If a sign-in page guards Portainer, let /api/system/status through so the check can reach it. The remote access guide shows how.
How Tillarr checks Portainer
Without a key, Tillarr asks for /api/system/status to see that Portainer is up, and reads its version from the answer. Every request goes from your device straight to your server, never through us. Works with Portainer CE 2.
Questions
Why Portainer and not the Docker socket?
A Docker socket gives full control of the host. Portainer's API is safer to reach from a phone.
Does Portainer send notifications?
No. Tillarr shows container state when you open it.