Closed arsaboo closed 2 months ago
Hi, Are you using Docker for deployment?
I am using docker for deployment and followed the process listed in the docs. What should the SEARXNG_HOSTNAME be? How do I test it
or...do I have to have to deploy searxng separately?
@arsaboo yes... searxng-docker
@yokingma So, I am running searxng using the following:
version: "3.7"
services:
redis:
container_name: redis
image: docker.io/library/redis:alpine
command: redis-server --save 30 1 --loglevel warning
networks:
- searxng
volumes:
- redis-data:/data
cap_drop:
- ALL
cap_add:
- SETGID
- SETUID
- DAC_OVERRIDE
searxng:
container_name: searxng
image: docker.io/searxng/searxng:latest
networks:
- searxng
ports:
- "8080:8080"
volumes:
- ./searxng:/etc/searxng:rw
environment:
- SEARXNG_BASE_URL=https://${SEARXNG_HOSTNAME:-localhost}/
cap_drop:
- ALL
cap_add:
- CHOWN
- SETGID
- SETUID
logging:
driver: "json-file"
options:
max-size: "1m"
max-file: "1"
networks:
searxng:
ipam:
driver: default
volumes:
redis-data:
and I can access searxng using the IP address http://192.168.2.122:8080/
But I am still getting the same error. How do I change the SEARXNG_HOSTNAME?
It may be useful for you to create a complete docker compose file...to avoid such issues.
Same error even with:
version: "3.7"
services:
redis:
container_name: redis
image: docker.io/library/redis:alpine
command: redis-server --save 30 1 --loglevel warning
volumes:
- redis-data:/data
cap_drop:
- ALL
cap_add:
- SETGID
- SETUID
- DAC_OVERRIDE
searxng:
container_name: searxng
image: docker.io/searxng/searxng:latest
ports:
- "8080:8080"
volumes:
- ./searxng:/etc/searxng:rw
environment:
- SEARXNG_BASE_URL=https://${SEARXNG_HOSTNAME:-localhost}/
cap_drop:
- ALL
cap_add:
- CHOWN
- SETGID
- SETUID
logging:
driver: "json-file"
options:
max-size: "1m"
max-file: "1"
volumes:
redis-data:
See here for an example of a combined docker-compose file or it will be great if you can provide an example.
@arsaboo Thanks for your suggestion, I have added docker-compose file.
docker compose up -d
Sources are working now... but for some reason Ollama isn't working with the same URL (I do see Ollama running on that URL). I'll check and let you know
@arsaboo Maybe the docker can't access the host's network?
# wondows or mac
OLLAMA_HOST=http://host.docker.internal:11434
Ok...so it worked if I run the docker on the same computer where Ollama is running. I was unable to get Ollama working from another host. But I will close this issue as the original issue is fixed. I will create a few more issues[feature requests] for you to consider.
I was able to get it working using Ollama. I am getting the results, but the sources are not displayed.
Here's my
.env