Docs / Operations

Portainer

Optional instructions for deploying the repository's docker-compose.portainer.yml as a Portainer Stack.

Create a Stack

Portainer is optional

Vyline can be started and updated with Docker Engine and docker compose alone. Portainer is an optional management UI for hosts where you want to manage multiple containers graphically; it is not a Vyline dependency.

If you use Portainer, create a Stack from docker-compose.portainer.yml. The standard image is ghcr.io/tqmane/vyline:latest.

Update

Pull the latest image.
Update / Redeploy the Stack.
Confirm that the Vyline container was recreated.
Confirm that data/ and storage/ still use the same bind-mount destinations.

Android real chroot

On some Android real-chroot hosts, bridge-published ports conflict with Android routing/netfilter. Only if Portainer shows the same symptom, host networking can be used as a diagnostic workaround for the management UI. This is not the default configuration for normal Linux.

docker volume create portainer_data
docker run -d \
  --name portainer \
  --restart=always \
  --network host \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -v portainer_data:/data \
  portainer/portainer-ce:latest \
  --http-disabled

https://<host-ip>:9443

Treat the Docker socket as privileged

Portainer can control host containers because it can access /var/run/docker.sock. Never expose the management UI directly to the Internet without authentication.