Portainer is a lightweight sexy UI for visualizing your docker environment. It also happens to integrate well with Docker Swarm clusters, which makes it a great fit for our stack.
This is a companion discussion topic for the original entry at https://geek-cookbook.funkypenguin.co.nz/recipies/portainer/
I guess the compose file for portainer is missing the internal networking overlay something like:
- subnet: 172.16.13.0/24
Am I right?
Actually no - Since there’s only one container in the whole stack (so it doesn’t need to be connected to any other “internal” containers), it only needs to connected to traefik_public so that Traefik can reach it.
If we were using an oauth_proxy here (which we can’t, currently, because of how portainer authentication works) then portainer could be on the internal network, and the oauth_proxy could be on both traefik_public and the internal network.