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’m using Proton mail, I like their focus on privacy and e2e (only with other Proton users, though).

All five of them.

Doesn’t it break a lot of things? Half the stuff refuses to work when some specific files have too permissive chmod.

I was talking about Nintendo, they constantly sue people (and other companies) for obscure amounts of money just because they’re rich and can afford it.

Well, Fedora 40 here as well and it just doesn’t work on my computer. Sure, Nvidia, blah blah blah. X does work flawlessly on my machine, though.

Like trying to destroy people’s lives so they can make a few dollars.

We use .lh, short for localhost. For local network services I use service discovery and .local. And for internal stuff we just use a subdomain of our domain.

I personally only turn it off when someone’s visiting over night and the noise disturbs them, otherwise I just leave it on nonstop. Mainly because it would annoy me to try to open whatever and find out I have to turn on the server first. I don’t have a UPS and never even thought about getting one (for the server, I’m thinking of getting one for my 3D printer).

Weird way to spell NixOS.

I use Proton Mail for my primary domain and then addy.io for redirects to it. It costs $10 a year or something like that and it’s all I actually need.

Replying to emails is as easy as just hitting reply, the only thing that’s slightly harder is sending entirely new email (as in not replying) but even that can either be remembered, or the special email address copied from the addy.io app.

Android is not really Linux, as has been explained about a bazillion of times. It uses a Linux kernel, doesn’t make it a Linux distribution.

Yeah, I need GPU for CUDA, so it needs to work. It also doubles as my gaming laptop, which I could live without, but it would be suboptimal.

Installation worked, it was just the usual Nvidia stuff and this time it was way above my skills.

Well, my laptop doesn’t have an ethernet port. When it happened to me (not on Debian, I think Mint or something), I didn’t even use a phone OS that was capable of sharing my internet via USB. Fun times.

Lucky you, straight up doesn’t work on my new laptop.

I did this once on my laptop with no backups. I was lucky. I also used the correct version with --no-preserve-root.

Avahi basically broadcasts to the whole network “hello there, my name is some-cool-domain.local”. When you request that address, your router checks if someone broadcasts that name and uses their IP if so.

Yes, indeed, it’s your local timezone.