Hacker News Reader

I am (was) using portainer on my host to manage my docker containers.

Turns out everything was, indeed, publicly accessible. I could fix it for my custom containers, by binding on 127.0.0.1:<port>, but I can't edit portainer's config.

Anyone has a solution for this?

View on HN

You can't fix this issue by binding to 127.0.0.1

My solution has always been to just use some external firewall (outside of the docker host machine.) Often cloud providers have this as a feature, to configure a firewall for your vps/network.

Does that really protect me against the "routing through" my machine they explain?

Reply on news.ycombinator.com