#community-help

Docker Compose Issue with Connecting Server and Typesense

TLDR Priyank couldn't connect their server with typesense through Docker compose. After troubleshooting with Kishore Nallan and WL, user discovered that they needed to specify the IP address of the typesense service in their client configuration.

7mo

Join the chat

Feb 02, 2023 (7 months ago)

Photo of md5-a9a351e11d64f05b41fec183816a0cda

Priyank

06:57 AM

I am using docker compose to run my server and typsense side by side but for some reason my server in container is not able to connect with typesense. please can anyone help me ?

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

07:13 AM

Did you expose port 8108 for docker?

Priyank

07:19 AM

actually i am kind of new to this docker ecosystem this is my compose config please check if there's any error

07:19

Priyank

07:19 AM

version: "3"
services:
typesense:
image: typesense/typesense:0.22.2
command: "--data-dir /data --api-key=ecommerce"
ports:
- "8108:8108"
volumes:
- typesense-data:/data
expose:
- "8108"

node-app:
depends_on:
- typesense
build: .
ports:
- "8000:8000"
environment:
- PORT=8000

volumes:
typesense-data:
driver: local

Kishore Nallan

07:25 AM

Check if the volume directory used typesense-data actually exists. You can also check the container logs to see if Typesense actually starts.

Priyank

09:12 AM

yeah i checked typesense starts fine but my nodejs server is not able to connect to it

Kishore Nallan

09:33 AM

This is likely a Docker compose configuration issue. I'm not super familiar with that, so you can probably get better help on Stackoverflow.

Photo of md5-e18fd6bf1ed8f3adba05f7061edef1e1

WL

10:09 AM

The enable-cors flag needs to be specified so that the server can be called from a frontend?

Kishore Nallan

10:13 AM

Yes but it's enabled by default

Priyank

10:24 AM

i figured it out ! in case of docker compose you have to specify ip address of typesense service in typesense client configuration in nodejs server

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2764 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Configuring Docker-hosted Typesense with Let's Encrypt SSL Certificates

Ian asked for help with setting up SSL certificates in a Docker-hosted Typesense. Jason provided suggestions but the issue remains unresolved due to port conflict.

5mo

Server IP Address and Port Issues with Typesense

Alex encountered problems with Typesense server configuration when setting IP and port using --api-address and --api-port, facing additional problems with CORS and version inequities. Kishore Nallan addressed each point, ultimately finding a bug with the command line parser affecting subsequent commands. The advised workaround was to use `--enable-cors=true`.

17mo

Troubleshooting Typesense Server Start-Up Process with Docker

gun asked how to start the Typesense server using Docker, which Jason explained. Monk added it also works on Windows 10 without Docker and agreed to add these details to documentation.

21mo

Resolving CORS Error in Typesense Server Setup

Digamber had a CORS error with Typesense server setup. Kishore Nallan solved the error by suggesting to use only `--enable-cors` without adding `=true`.

21mo

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.

10mo