Docker docs:

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.

    • grrgyle@slrpnk.net
      41·
      5 days ago

      I exposed them because I used the container for local development too. I just kept reseeding every time it got hacked before I figured I should actually look into security.

      • MangoPenguin@lemmy.blahaj.zoneEnglish
        19·
        5 days ago

        For local access you can use 127.0.0.1:80:80 and it won’t put a hole in your firewall.

        Or if your database is access by another docker container, just put them on the same docker network and access via container name, and you don’t need any port mapping at all.

        • grrgyle@slrpnk.net
          1·
          4 days ago

          Yeah, I know that now lol, but good idea to spell it out. So what Docker does, which is so confusing when you first discover the behaviour, is it will bind your ports automatically to 0.0.0.0 if all you specify is 27017:27017 as you port (without an IP address prefixing). AKA what the meme is about.

        • grrgyle@slrpnk.net
          1·
          4 days ago

          My use case was run a mongodb container on my local, while I run my FE+BE with fast live-reloading outside of a container. Then package it all up in services for docker compose on the remote.

          • Ethan@programming.devEnglish
            2·
            3 days ago

            Ok… but that doesn’t answer my question. Where are you physically when you’re working on this that people are attacking exposed ports? I’m either at home or in the office, and in either case there’s an external firewall between me and any assholes who want to exploit exposed ports. Are your roommates or coworkers those kinds of assholes? Or are you sitting in a coffee shop or something?

            • grrgyle@slrpnk.net
              1·
              3 days ago

              This was on a VPS (remote) where I didn’t realise Docker was even capable of punching through UFW. I assumed (incorrectly) that if a port wasn’t reversed proxied in my nginx config, then it would remain on localhost only.

              Just run docker run -p 27017:27017 mongo:latest on a VPS and check the default collections after a few hours and you’ll likely find they’re replaced with a ransom message.