#community-help

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.

Powered by Struct AI
5
6mo
Solved
Join the chat
Apr 12, 2023 (6 months ago)
Pallavi
Photo of md5-d8172bec3bfc4e0dcb58cd7347169298
Pallavi
07:40 AM
Hi all,
I am trying to configure typesense via docker in my local system. I am facing some error, can someone help me?
Jason
Photo of md5-8813087cccc512313602b6d9f9ece19f
Jason
07:44 AM
Could you share the exact command you ran and the output?
Pallavi
Photo of md5-d8172bec3bfc4e0dcb58cd7347169298
Pallavi
11:20 AM
Hey Jason,
I 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=Hu52dwsas2AdxdE

Now 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"}
12:26
Pallavi
12:26 PM
Hey Jason,
Update:
8108 Port has been killed. But I am still getting error of { "message": "Not Found"}. Please find below screenshot of logs.
Image 1 for Hey Jason,
Update:
8108 Port has been killed. But I am still getting error of { "message": "Not Found"}. Please find below screenshot of logs.
Jason
Photo of md5-8813087cccc512313602b6d9f9ece19f
Jason
02:10 PM
From the logs it looks like the cluster is up. The root endpoint will return a 404. You want to hit the /health endpoint to check if the server is healthy