I hostes searxng on portainer but I still can’t seem to access http://mydomainname/20054/

Also portainer doesn’t show any Published Ports (it shows 20054:8080 for a very short period when I start the stack and then disappeared)

version: "3.7"

services:
  # caddy:
  #   container_name: caddy
  #   image: docker.io/library/caddy:2-alpine
  #   network_mode: host
  #   restart: unless-stopped
  #   volumes:
  #     - /volume1/SN/Docker/searxng-stack/Caddyfile:/etc/caddy/Caddyfile:ro
  #     - caddy-data:/data:rw
  #     - caddy-config:/config:rw
  #   environment:
  #     # - SEARXNG_HOSTNAME=${SEARXNG_HOSTNAME:-http://localhost/}
  #     - SEARXNG_TLS=${LETSENCRYPT_EMAIL:-internal}
  #   cap_drop:
  #     - ALL
  #   cap_add:
  #     - NET_BIND_SERVICE
  #   logging:
  #     driver: "json-file"
  #     options:
  #       max-size: "1m"
  #       max-file: "1"

  redis:
    container_name: redis
    image: docker.io/valkey/valkey:8-alpine
    command: valkey-server --save 30 1 --loglevel warning
    restart: unless-stopped
    networks:
      - searxng
    volumes:
      - valkey-data2:/data
    cap_drop:
      - ALL
    cap_add:
      - SETGID
      - SETUID
      - DAC_OVERRIDE
    logging:
      driver: "json-file"
      options:
        max-size: "1m"
        max-file: "1"

  searxng:
    container_name: searxng
    image: docker.io/searxng/searxng:latest
    restart: unless-stopped
    networks:
      - searxng
    ports:
      # - "127.0.0.1:8080:8080"
      - "20054:8080"
    volumes:
      - /volume1/SN/Docker/searxng-stack/searxng:/etc/searxng:rw
    environment:
      # - SEARXNG_BASE_URL=https://${SEARXNG_HOSTNAME:-localhost}/
      - SEARXNG_BASE_URL=http://mydomainname/20054/
      - UWSGI_WORKERS=${SEARXNG_UWSGI_WORKERS:-4}
      - UWSGI_THREADS=${SEARXNG_UWSGI_THREADS:-4}
    cap_drop:
      - ALL
    cap_add:
      - CHOWN
      - SETGID
      - SETUID
    logging:
      driver: "json-file"
      options:
        max-size: "1m"
        max-file: "1"

networks:
  searxng:

volumes:
  # caddy-data:
  # caddy-config:
  valkey-data2:

thx a lot!

  • HappyTimeHarry@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    7 days ago

    open(“/etc/searxng/uwsgi.ini”): Permission denied [core/io.c line 525]

    I think here is your problem. Make sure that file exists and is readable from inside of the docker.

      • HappyTimeHarry@lemm.ee
        link
        fedilink
        English
        arrow-up
        0
        ·
        7 days ago

        try opening a shell with ’ docker exec -it searxng sh" and see if you can cat the file from inside docker, if yes then I’m not sure of a solution ,if no then the problem is with permissions on your filesystem outside of docker where you have " - ./data/searxng:/etc/searxng" You need to go to ./data/searxng and correct the permissions so they can be read inside the docker.

        • Override4414@lemmy.worldOP
          link
          fedilink
          English
          arrow-up
          0
          ·
          7 days ago
          ~ # ls /etc/searxng
          settings.yml  uwsgi.ini
          ~ # cat settings.yml
          cat: can't open 'settings.yml': No such file or directory
          ~ # cat /etc/searxng/settings.yml
          general:
            # Debug mode, only for development. Is overwritten by ${SEARXNG_DEBUG}
            debug: false
            # displayed name
            instance_name: "searxng"
            # For example: https://example.com/privacy
          

          I think I do have the permission?

          • HappyTimeHarry@lemm.ee
            link
            fedilink
            English
            arrow-up
            0
            ·
            7 days ago

            Yep Probably you need to change ownership and/or permissions of the files outside of docker.

            I dont want to give the wrong suggestion from memory so hopefully thats enough info to get you going in the direction of a fix. Basically see what user id owns the files inside of docker, make it the same uid outside of docker in the folder you are bind mounting.

            • Override4414@lemmy.worldOP
              link
              fedilink
              English
              arrow-up
              0
              ·
              edit-2
              7 days ago
              SN_FR_@SN:~$ sudo docker exec -it searxng sh -c "id"
              uid=0(root) gid=0(root) groups=0(root)
              

              container is running as root, so there shouldn’t be any permission error?

              u are right its not writable, the files are read only, that is wierd

              I’m opening those files with windows but the user permission inside docker shouldn’t cause that problem.

              I’m scratching my head nw