Hello, ive seen a lot of tools made only for docker and kubernetes and i will like to know if someone can run docker safely while running a hidden service using it.and if docker whill give the law enforcement info about the hoster
Programming
is Docker privacy & policy a security threat when running a hidden service
Started by Germany · Oct 23, 2025
Docker is not a VM and should not be treated as such, it is a containerized system. That means that normal security practices apply when using Docker. The images Docker uses are normally pulled from Dockerhub, as such Dockerhub can see that you are pulling said images. If you don't want to pull a prebuild image, you can just pull the baseimage (Debian, Alpine, etc.) and build the image yourself.
If I interpret your question correctly you are concerned with the the Dockerengine posing a thread. If you think that is the case you can use Podman. Alternatively you can just install said tool directly on your server, there are no "tools made only for docker" as Docker is just an containerized OS. That being said containers have the advantage of being quick to spin up, but to a given scale you don't need that.
If I interpret your question correctly you are concerned with the the Dockerengine posing a thread. If you think that is the case you can use Podman. Alternatively you can just install said tool directly on your server, there are no "tools made only for docker" as Docker is just an containerized OS. That being said containers have the advantage of being quick to spin up, but to a given scale you don't need that.
How about you read about Docker being open source and how it actually works?
Strictly speaking, using Docker is a better way to deploy a hidden service as breaking one container may not "leak" to the others. I would not recommend it on Debian-based systems, however. If you want to use Docker, then you should look to build off of RHEL-based systems since they use SELinux + Podman at its core. SELinux is a sort-of meta programming language to define how processes are allowed to use system resources, and Podman is a Docker replacement that applies good SELinux rules.
Debian-based systems use something called apparmor, but they don't have this same level of built in security.
Of course with Docker you can do things like detach networking, have limited filesystems etc too, which is a nice-to-have. It's also a lot easier to wrangle something like a container to pipe all its networking through Tor than it is to iptables your whole server (although you should probably do both!)
Debian-based systems use something called apparmor, but they don't have this same level of built in security.
Of course with Docker you can do things like detach networking, have limited filesystems etc too, which is a nice-to-have. It's also a lot easier to wrangle something like a container to pipe all its networking through Tor than it is to iptables your whole server (although you should probably do both!)
For privacy, if you build your own images then Docker only really "knows" you when you download the base layers, not every time you run it. It's open source software. You should obviously not push your own Docker images to a public container repository, but rather host your own or just ship Dockerfiles and tor-ify the process.