Portainer
gunkanmaki.portainer
A Docker Compose file for Portainer alone, generated from the catalog and checked by the safety inspector. No account needed.
Management interface for Docker, Docker Swarm and Kubernetes covering container, image, volume, network and stack lifecycle, with role-based access across several attached environments.
Portainer connects to a container runtime through its API and presents what it finds — containers, images, volumes, networks, stacks — as a browsable interface with the usual lifecycle actions, log viewing and an in-browser console into a running container. Several environments can be attached through agents, so one console covers more than a single host or cluster. Access is granted per team and per environment, and application templates and Git-backed stacks give a deployment path for people who do not hand-write Compose files. A first deployment creates the administrator account inside the initial timeout window and attaches the local environment.
You know it worked when
- The interface loads and the administrator account can be created and used to sign in.
- The local environment is attached and lists running containers.
- Container logs are readable through the interface.
- A stack deployed from a Compose definition starts and its containers appear.
- A second user restricted to one environment cannot see the others.
Known sharp edges
- The administrator account must be created within a few minutes of first start, or the instance locks itself and has to be restarted before setup can continue.
- It requires access to the Docker socket, which gives the container effective root on the host unless a filtering proxy sits in front of it.
- Any account able to open a console into a container inherits whatever privileges that container holds.
- Business Edition features appear in the interface and prompt for a licence key rather than being hidden, which makes the edition boundary easy to misread.