You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. I'm trying to get a self-hosted SigNoz running on my server via plain Docker Compose. Checking the compose file, I noticed that it publishes a number of ports by default. Unfortunately, it is a known and longstanding issue in Docker that publishing container ports punches holes in the firewall, exposing them to the public. I'd like to lock down the access as much as possible. With that in mind, how should I adjust the default configuration? What services need to be exposed publicly and what can be left isolated on the bridge network/host machine? Thanks in advance.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi. I'm trying to get a self-hosted SigNoz running on my server via plain Docker Compose. Checking the compose file, I noticed that it publishes a number of ports by default. Unfortunately, it is a known and longstanding issue in Docker that publishing container ports punches holes in the firewall, exposing them to the public. I'd like to lock down the access as much as possible. With that in mind, how should I adjust the default configuration? What services need to be exposed publicly and what can be left isolated on the bridge network/host machine? Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions