• 681 Posts
  • 3.76K Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle





    1. For all the mentioned cases, if your firewall blocks incoming packets by default, no one can access it, no matter what is the source of the port being open.

    2. You don’t configure it on the docker level, at least if you care about outside connections. If you mean from your local computer to a docker container, by default you cannot connect, unless you expose the port to the system. If you mean from other docker containers, just create your own separate network to run the container in and even docker containers cannot access the ports.

    3. I usually use netstat -tulpn, it lists all ports, not only docker, but docker is included. docker ps should also show all exposed ports and their mappings.

    In general, all docker containers run on some internal docker network. Either the default or a custom one. The network’s ports don’t interfere with your own, that’s why you can have 20 nginx servers running in a docker container on the same port. When you bind a port in docker, you basically create a bridge from the docker network to your PC’s local network. So now anything that can connect to your PC can also connect to the service. And if you allow connection to the port from outside the network, it will work as well. Note that port forwarding on your router must be set up.

    So in conclusion, to actually make a service running in docker visible to the public internet, you need to do quite a few steps!

    • bind a port to your local host
    • have your local firewall allow connection to the port
    • have your router set up to forward connections on the port to your machine

    On Linux, local firewall is usually disabled by default, but the other two steps require you to actively change the default config. And you mention that all incoming traffic is dropped using UFW, so all three parts should be covered.






  • I mean, sure, but this could be the push to open architecture. Half the apps wouldn’t need recompiling anyway, only those containing native code.

    Realistically it could take 2-3 years for Qualcomm to switch to RISC-V (so 5 years because we all know how smooth such huge transitions are). That’s enough time for Google to fully support Android on RISC-V.

    IMO it’s now in Google’s hands, once they add support, interesting things are gonna happen. I could even see Arm going out of business, I’m sure Qualcomm would happily help others transition for a very fair fee to help get them out of business.

    I think with RISC-V being as supported as it is (meaning it’s nothing obscure, but has strong open source toolchain support), this might potentially be a very bad move for Arm.

    Anyway, I love it when corporate greed destroys corporations instead of humans for a change. And if open architecture gains traction thanks to that, well, all the better.