• 4 Posts
  • 7 Comments
Joined 2 years ago
cake
Cake day: October 4th, 2023

help-circle


  • Note that I’m running it on a rootless docker instance, and NOT on Podman. So, the following solution might or might not work for you.

    services:
      degoog:
        image: ghcr.io/fccview/degoog:latest
        volumes:
          - ./.data:/app/data
        user: "0:0"
        ports:
          - "4444:4444"
        restart: unless-stopped
    

    Explanation: rootless docker works a bit different from rootful docker. user 1000 (which is you on your server/machine) will be mapped to a different UID (e.g. 32555). This is to ensure that any process in docker container can’t have access to folders/files that you have access to, in case it manages to break free of docker containerization.

    When you put user: “0:0” in a rootless docker container, it will assume your UID 1000 (which is you on your server/machine) inside docker container.

    While it solves the file permission issue, but it is NOT a recommended way.

    with user:1000:1000

    with user:0:0



  • First of all, thanks a ton.

    I have been using SearxNG for more than year, running it as docker container on my Homelab. It’s connected to internet via Mullvad VPN.

    Lately, I have see both Google and Bing search engines are either not working or returning complete garbage results.

    My firewall setup doesn’t allow any incoming connection to homelab, except from LAN. So, bot accessing my SearxNG instance might not be the issue.

    With degoog installed in the same fashion (docker + VPN), google engine seems to be unblocked for me (so far).

    Not sure why degoog is not getting rate limited like SearxNG on the same system and same VPN. But, at least I’m happy :)