Configuring Typesense via Docker and Resolving "Not Found" Error
TLDR Pallavi encountered issues while configuring typesense via docker, including a "Not Found" error message. Jason advised to hit the /health endpoint to check the server's health.
Apr 12, 2023 (6 months ago)
Pallavi
07:40 AMI am trying to configure typesense via docker in my local system. I am facing some error, can someone help me?
Jason
07:44 AMPallavi
11:20 AMI was using below commands:
mkdir /tmp/typesense-data
docker run -p 8108:8108 -v/tmp/data:/data typesense/typesense:0.24.1 --data-dir /data --api-key=Hu52dwsas2AdxdENow I am facing two issues:
1. The 8108 is already in use error but at the same time if i am checking whether any process is running or not, I found out that no process is running.
2. I made changes in the command and mapped 8106:8108, but still I am unable to get expected output. The output which I am getting right now is:
{ "message": "Not Found"}
Pallavi
12:26 PMUpdate:
8108 Port has been killed. But I am still getting error of { "message": "Not Found"}. Please find below screenshot of logs.
Jason
02:10 PM
Typesense
Indexed 2779 threads (79% resolved)
Similar Threads
Troubleshooting Typesense Server Error on Docker
vikram was facing an error with Typesense Server Docker container and loss of data on restart. Kishore Nallan guided to avoid mounting tmp directory from localhost and explained stopping the Docker container.
Running Typesense in Docker Container on Windows 10
Christian had issues running Typesense in Docker due to an unrecognized data directory. Jason suggested a solution to fix the file path issue, which Christian successfully implemented using Windows Powershell.
Facing Troubles in Understanding Typesense Version and Configuration
andy couldn't identify the Typesense server version and faced an invalid configuration error. Kishore Nallan suggested accessing version through `/debug` and clarified that the configuration error may not matter if Docker isn't being used. andy confirmed a local installation.