Docker routes container traffic in the nat table, which means that packets are diverted before it reaches the INPUT and OUTPUT chains that ufw uses. Packets are routed before the firewall rules can be applied, effectively ignoring your firewall configuration.

you are viewing a single comment's thread
view the rest of the comments

[–] sidelove@lemmy.world 14 points 2 weeks ago (2 children)

have to make sure of is that the deployment environment has node and the angular CLI installed

I have spent so many fucking hours trying to coordinate the correct Node version to a given OS version, fucked around with all sorts of Node management tools, ran into so many glibc compat problems, and regularly found myself blowing away the packages cache before Yarn fixed their shit and even then there's still a serious problem a few times a year.

No. Fuck no, you can pry Docker out of my cold dead hands, I'm not wasting literal man-weeks of time every year on that shit again.

(Sorry, that was an aggressive response and none of it was actually aimed at you, I just fucking hate managing Node.js manually at scale.)

[–] TrickDacy@lemmy.world 3 points 2 weeks ago

I agree, for any context that it makes sense, docker is so worth it

[–] peoplebeproblems@midwest.social 0 points 2 weeks ago

Well, I guess that's a good reason. Node version management seems to handle most of that for me though. I haven't worked on an OS without support for it.