Comment on [beta] degoog - search engine aggregator

• thestrike@lemmy.blahaj.zone ⁨5⁩ ⁨days⁩ ago

  I had the same problem so let me know if you find a solution! I just switched to running as root with podman

  source

  • KarnaSubarna@lemmy.ml ⁨3⁩ ⁨days⁩ ago

    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

    Image

    with user:0:0

    Image

    source

    • thestrike@lemmy.blahaj.zone ⁨3⁩ ⁨days⁩ ago

      Is there a recommended way to do it? Could I give file permissions to the UID that docker has or something? Or put docker in the same user group as me

      source
• fccview@lemmy.world ⁨6⁩ ⁨days⁩ ago

  Hey, not sure what you mean, it works perfectly fine as rootless. Are you using docker or podman? Someone else had this issue with podman and we couldn’t figure out why it was different for them.

  Everyone else is running this as user 1000, which is what the standard compose requires?

  source

  • KarnaSubarna@lemmy.ml ⁨3⁩ ⁨days⁩ ago

    Please refer to this comment: lemmy.ml/comment/24567541

    If you need any further information, let me know.

    source