overview for TheFrogThatFlies

*Permanently Deleted* in c/technology@lemmy.world

[–] TheFrogThatFlies@lemmy.world 199 points 4 weeks ago (3 children)

Wait! Think about the children! What if we need to track pedophiles!?

Restricted Tailscale docker instance in c/selfhosted@lemmy.world

[–] TheFrogThatFlies@lemmy.world 2 points 1 month ago (1 children)

I have a single server with everything inside. By using Tailscale to access my server I'm giving full access to it and the entirety of my network to a third party tool that I don't know that well.

13

Restricted Tailscale docker instance (lemmy.world)

submitted 1 month ago* (last edited 1 month ago) by TheFrogThatFlies@lemmy.world to c/selfhosted@lemmy.world

11 comments fedilink

My ISP uses CG NAT which is stopping me from reaching my internal network, so I'm thinking about using Tailscale to allow me to connect to my server and hence to my internal network.

But I'm not very comfortable giving 100% access to Tailscale to my internal network, so I was thinking if I could limit it only to what it requires to connect to the internet and to a wireguard service running in the same container. This would in turn connect to a wireguard server in the container's host and provide me with full network access.

I know, as long as they have a service running in the server, even if inside a container, they can always be able to access the host. But even do I would feel safer if at least tried to contain it.

Does anyone know if this is possible? And can it be done through Docker Compose?