2 ms·
Its documented, but still extremely surprising even for experienced docker users. The only place you will read about this is is you actually go to the docs page
by JamesSwift 4y ago
Its documented, but still extremely surprising even for experienced docker users. The only place you will read about this is is you actually go to the docs page for the `-p` flag. But as I've said before, why would I do that? I already know what `-p` does (spoiler: I didn't know what it did).
It was multiple years before I realized I was exposing my services like this, after it came up on HN a while back.
- k8sToGo 4y agoI am not saying that this does not suck. I was a victim of this as well. I am just saying that it isn't really negligence, just bad architecture.
- JamesSwift 4y agoRight, but theres bad architecture and then theres "this is a security risk and every tutorial in the wild + every app in production uses this in an insecure way and we haven't done anything about it". I just realized I posted my thoughts on this github issue [1] which is now _six_ years old. There have been no updates / changes made as far as I can tell. [1] - https://github.com/moby/moby/issues/22054 https://github.com/moby/moby/issues/22054
- k8sToGo 4y agoMhh good point. I guess if you keep bad architecture long enough it becomes negligence.