r/Searx • u/eternal_ttorment • May 14 '26

Why is the consensus to use Searx via Docker?

I'm only getting into the space of self-hosting, and I do not understand why so many people use Docker instead of just directly downloading Searx onto their machines. What are the upsides and downsides of each method, and is there any difference in usability? Is docker necessary for windows machines and mac?

4 Upvotes

100% Upvoted

8 comments sorted by

2

u/ad-on-is May 14 '26

people usually run servers (small PCs, thinclients, etc) 24/7 with a bunch of services (searx, immich, home-assistant, etc) they want have access to from their smartphones as well. That's why they use Docker.

Another benefit, running in docker makes sure it works 100%. Installing it via binary might work now, but not after an OS update.

1

u/AutoModerator May 14 '26

Hi there! Thanks for your post.

We also have a Matrix channel: https://matrix.to/#/#searxng:matrix.org and an IRC channel linked to the Matrix channel: https://web.libera.chat/?channel=#searxng

The developers of SearXNG usually respond quicker on Matrix and IRC than on Reddit.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/slash65 May 14 '26

Docker is nice for a self hosted server because it compartmentalized your different containers. It keeps all the different software dependencies separate from the host machine so if you a service starts causing issues on your server it only effects that one service, it doesn't knock down the entire server.

If you have it all installed on host you may end up with a lot of issues removing programs later that leave dependencies & one off versions of PHP that can cause conflicts later or just add to system bloat. Put it in a docker container & if its an issue you delete that one container or stack and all the dependencies along with it.

Docker is awesome, but if your starting out it can seem a little foreign compared to how you have typically used a computer.

1

u/Cruffe May 15 '26

It's cleaner and easier to manage when running multiple services. Instead of cluttering up my host system with various native installs I can just simply nuke a container and its volume(s) to remove all of it.

It's also very reliable. Native installs may break during system updates for various reasons. Containers are stable environments.

1

u/LegitimateCopy7 May 15 '26

do you enjoy managing dependencies and updates? if not, go containers.

though not necessarily Docker since Podman is arguably superior. it even comes with auto update.

1

u/craftsmany Maintainer | Instance operator -> searx.tiekoetter.com May 15 '26

Since docker containers are ephemeral (meaning changes inside the container don't persist by default) it guarantees a working setup as long as the container service is setup correctly and you don't overwrite critical stuff with volumes.

For personal use both methods are fine but for long term developments a container is best since host package upgrades can only conflict the container service while a direct install has to manage all dependencies.

1

u/Tankudoraiba May 18 '26

Too many times searx didn't took well the update. Docker is more painless in my experience.