5 ms·

Are you binding to 127.0.0.1 or 0.0.0.0? > Sure, you should keep the containers talking within the docker network, but we are kind of distributed in our org (a

Are you binding to 127.0.0.1 or 0.0.0.0? > Sure, you should keep the containers talking within the docker network, but we are kind of distributed in our org (across a series of NUCs). I don’t think I understand this, are you saying that you want the ports exposed to some devices on your network but not others?

teekert 2y ago
In docker-compose it's just "- ports", I guess it's always 0.0.0.0, unless bound to something else (like 127.0.0.1). You can restrict it to the Tailnet IP, but then you have to hardcode the Tailscale 100.x.x.x IP address (not flexible).