Self-Host Whoogle Search with Docker: Private Metasearch A developer documented a Docker Compose deployment for Whoogle Search, a self-hosted metasearch front end that fetches Google results server-side and strips ads, JavaScript, AMP links, cookies and IP tracking. The guide notes that Whoogle reached end of life on 24 July 2026 after Google shut down the non-JavaScript search path it relied on, so the code and MIT-licensed Docker images remain available for running, forking or study but no longer return live Google results. The setup uses a non-root user, dropped capabilities, no-new-privileges, tmpfs mounts and a 256 MB memory cap, with basic auth, Tor and proxy options and a Caddy or Nginx reverse proxy for TLS. This tutorial was written with AI assistance from the project's official documentation. Verification status is stated at the end of the article. Whoogle Search is a self-hosted metasearch front end that fetches Google results server-side and serves them without ads, JavaScript, AMP links, cookies, or IP tracking. Your browser talks only to your instance; the instance talks to Google. It supports Tor and HTTP/SOCKS proxies, custom bangs, JSON output, and basic auth. Important status note: the upstream README states that Whoogle reached end of life on 24 Jul 2026. Google shut down the non-JavaScript search path Whoogle relied on, and the project is no longer maintained. The code and Docker images remain available under MIT, but a fresh deployment will not return live Google results today. This guide documents the last known-good Docker deployment so you can run, fork, or study it. The project does not publish a minimum RAM figure. The official Compose file caps the container at 256 MB with a 50-process limit, which is a sensible ceiling for a single-user instance. Idle memory is small; concurrent searches and Tor routing push it toward that cap. docker compose version . localhost is fine. 127.0.0.1:5000 so it is not exposed unencrypted on the public IP. whoogle user UID/GID 927 and expects writable tmpfs mounts at /config/ , /var/lib/tor/ , and /run/tor/ . These are ephemeral by design; no named volume is required for normal operation. linux/amd64 and linux/arm64 . ARMv7 32-bit is not supported in v1.2.0+. If you are testing without a domain, either SSH-tunnel to the bound port ssh -L 5000:127.0.0.1:5000 user@host or temporarily change the port mapping to 5000:5000 and remove it after testing. Create a project directory and drop in the Compose file. It mirrors the official structure: non-root user, dropped capabilities, no-new-privileges , tmpfs mounts, and resource limits. mkdir -p ~/whoogle && cd ~/whoogle cat <<'EOF' compose.yml services: whoogle-search: image: ${WHOOGLE IMAGE:-benbusby/whoogle-search:latest} container name: whoogle-search restart: unless-stopped pids limit: 50 mem limit: 256mb memswap limit: 256mb user: whoogle security opt: - no-new-privileges:true cap drop: - ALL tmpfs: - /config/:size=10M,uid=927,gid=927,mode=1700 - /var/lib/tor/:size=15M,uid=927,gid=927,mode=1700 - /run/tor/:size=1M,uid=927,gid=927,mode=1700 environment: - TZ=${TZ:-UTC} - WHOOGLE USER=${WHOOGLE USER} - WHOOGLE PASS=${WHOOGLE PASS} - WHOOGLE URL PREFIX=${WHOOGLE URL PREFIX:-} - WHOOGLE CONFIG TOR=${WHOOGLE CONFIG TOR:-0} - WHOOGLE PROXY TYPE=${WHOOGLE PROXY TYPE:-} - WHOOGLE PROXY LOC=${WHOOGLE PROXY LOC:-} - WHOOGLE PROXY USER=${WHOOGLE PROXY USER:-} - WHOOGLE PROXY PASS=${WHOOGLE PROXY PASS:-} ports: - 127.0.0.1:5000:5000 EOF Now create the .env file. Generate real secrets instead of typing passwords: cat <