Optional Portainer
Optional Portainer usage for operators who want a graphical Docker management tool alongside MatrixEasyMode.
Portainer is an optional operator convenience. It is not required to install, run, or upgrade MatrixEasyMode.
Use it when you specifically want a graphical Docker management interface. If you do not need that, skip it.
MatrixEasyMode is designed to be operable from the shell using the standard helper scripts and Docker Compose workflow.
Portainer exists as an optional tool for operators who want a graphical view of containers, images, volumes, networks, and service state.
It should be treated as a convenience layer, not part of the core MatrixEasyMode runtime.
When to use Portainer
Use Portainer when you want to:
- inspect containers visually
- review Docker state in a UI
- confirm service status without relying entirely on shell commands
- inspect images, volumes, or networks from a graphical interface
Do not treat Portainer as required for normal MatrixEasyMode operation.
For most operators, the default workflow should still be:
- use
install.shfor setup - use
stack.shfor lifecycle operations - use logs and status first
- use optional tooling only when it adds real value
Why this sits under Tools
Portainer belongs under Tools because it is:
- optional
- operator-facing
- separate from the core application runtime
- helpful for some operators, but not part of the main install path
That keeps the docs structure clean and helps avoid implying that MatrixEasyMode depends on Portainer.
Start Portainer
Use the helper script:
./tools.sh portainer startCheck Portainer status
./tools.sh portainer statusView Portainer logs
./tools.sh portainer logsStop Portainer
./tools.sh portainer stopOperator guidance
A good workflow is:
- get the core MatrixEasyMode stack healthy first
- use
./stack.sh statusand logs to confirm the real runtime state - only then bring up Portainer if you want a visual Docker view
This keeps the operational model clear.
Portainer can be useful, but it should not become a substitute for understanding the actual runtime model.
What Portainer is helpful for
Portainer is most useful when you want to visually inspect:
- running and stopped containers
- image state
- network attachments
- volume state
- container restart or recreation behavior
It can be a nice companion tool, especially for operators who want both shell and UI visibility.
What Portainer does not replace
Portainer does not replace the core MatrixEasyMode docs or operator workflow.
You still need to understand:
- staged startup order
- Nginx Proxy Manager prerequisites
- wildcard certificate requirements
- public URL and DNS alignment
- registry mode versus local mode
- environment-driven configuration
If MatrixEasyMode is not starting correctly, begin with the normal troubleshooting sequence first.
Safety posture
Portainer makes Docker state easier to view, but graphical convenience should not lead to random changes.
When something looks wrong, start here:
./stack.sh status
./stack.sh logs infra
./stack.sh logs appThen use Portainer as a supporting tool if visual inspection helps.
Keep the boundary clear
Portainer is not part of the core MatrixEasyMode runtime.
The core runtime remains:
postgresnpmapiweb
Portainer is an optional operator convenience layered around the Docker environment.
That distinction helps prevent confusion in the docs and keeps the primary operator path disciplined.