4 ms·
You‘re wrong. If you use a command line argument that explicitely states „this will publish this port in your firewall for convenience“, a command line argument
by selfmodruntime 4y ago
You‘re wrong. If you use a command line argument that explicitely states „this will publish this port in your firewall for convenience“, a command line argument which you shouldn‘t use anyway, then you‘re on your own.
You choose to do this. Docker assumes that you know what you‘re doing.
You‘re also wrong in your last paragraph. There is the - easy - option to expose the port on your loopback, and re route to the docker bridge network by using a reverse proxy.
- nickstinemates 4y agoThis is exactly right. The alternative is ridiculous. Also, comparing expectations of Docker vs. something like nginx is crazy.
- allarm 4y ago> the alternative is ridiculous. Like what is, having full control over your own system? I don’t think there’s anything wrong with not messing with my firewall and leaving this part to me. > is crazy And this is why, exactly?
- Gordonjcp 4y agoHow exactly do you *not* have full control of your system? Because typing in a command expressly designed to modify firewall rules... actually modifies firewall rules?
- allarm 4y agoIt’s not clearly stated in the docs, this is exactly how and why that happens.
- Gordonjcp 4y agoIt actually is, though, you just need to read them.
- apple4ever 4y agoI read them. It's doesn't say that.
- selfmodruntime 4y agoYou do have full control over your system. You could choose not to install docker, for once.