#community-help

Trouble Running Typesense Docker Image on AMD Phenom II X4 955 Processor

TLDR Ian struggles to run Typesense on an AMD Phenom II X4 955 Processor, experiencing the docker image to shut down immediately upon startup. Jason and Kishore Nallan suggest multiple troubleshooting steps, identifying the potential issue as the processor's lack of support for MSSE4 flags.

14mo

Join the chat

Oct 17, 2022 (14 months ago)

Photo of md5-570c9110eca6a274b9a81eece83ee2dc

Ian

09:47 PM

Hi, I'm just trying out typesense but can't seem to get the docker image to work. Usually I use docker-compose so maybe I'm doing something wrong but it just starts up and then shuts down. Do I need to preload the data directory with information before I start the server ?

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

09:48 PM

Could you share the logs from the typesense container?

09:48

Jason

09:48 PM

You do need to mount a directory from the host and pass that into the container to use as the data dir

09:49

Jason

09:49 PM

https://typesense.org/docs/guide/install-typesense.html#from-the-docker-image

Ian

09:53 PM

$ sudo rm -Rf /tmp/typesense_data

$ mkdir /tmp/typesense_data; docker run -p8108:8108 -v/tmp/typesense_data:/data typesense/typesense:0.23.1 --data-dir /data --api-key=anything --enable-cors

$ docker ps -l

CONTAINER ID   IMAGE                        COMMAND                  CREATED         STATUS                       PORTS     NAMES

91cfa8a0e989   typesense/typesense:0.23.1   "/opt/typesense-serv…"   8 seconds ago   Exited (132) 6 seconds ago             pensive_mendeleev

$ docker logs 91cfa8a0e989
$

09:54

Ian

09:54 PM

Do you know what code 132 is ?

09:54

Ian

09:54 PM

Maybe I'm using the port or something.

Jason

09:55 PM

Is your host machine ARM by any chance?

Ian

09:55 PM

AMD Phenom(tm) II X4 955 Processor

09:56

Ian

09:56 PM

The logs appear completely empty.

09:56

Ian

09:56 PM

Is there an older version I should try ?

Jason

09:57 PM

Could you try adding --platform=linux/amd64 to the docker run command?

09:57

Jason

09:57 PM

I suspect Docker is somehow pulling the image for the wrong CPU arch, so it’s not even booting up for the Typesense binary to run

Ian

10:05 PM

Doesn't seem to change outcome.

10:08

Ian

10:08 PM

Is there an older version I could try ?

Jason

10:10 PM

It looks like AMD Phenom(tm) II X4 955 Processor was first released in 2009. Code 132 essentially means there was a CPU instruction that was sent that the CPU didn’t understand. So I suspect your processor’s instruction set doesn’t support the docker image.

We only started publishing Docker images in 2018, so I don’t think older versions of the Typesense docker image would work either…

Your best bet would be to rebuild the docker image on your host machine

Ian

10:10 PM

I deleted that image but it says I downloaded it 3 months ago, probably last time I tried it. Seems weird it would be broken that long and no one else would notice. Seems like some conflict with my setup maybe. I'm going to try to restart.

10:11

Ian

10:11 PM

Okay I'll maybe try that next or try running it on another machine.

10:11

Ian

10:11 PM

Thanks for your help, bbl.

Jason

10:12 PM

If you need to build the Docker image, here’s a one-liner: https://github.com/typesense/typesense#build-from-source

Ian

11:16 PM

Still 132, maybe I didn't build it correctly.

Jason

11:17 PM

Once you’ve built it, you want to use typesense/typesense:nightly as the image name in your docker run command

11:19

Jason

11:19 PM

Oh wait, just remembered that the build relies on another docker image that also needs to be rebuilt: https://github.com/typesense/typesense/blob/a1a77242b68d9bd0d6ca34eba3dfa9e4b542c444/docker-build.sh#L32

11:20

Jason

11:20 PM

So you want to rebuild this docker image: https://github.com/typesense/typesense/blob/main/docker/development.Dockerfile

And then use that development image in docker-build.sh instead

Ian

11:20 PM

The script didn't actually finish I had to try to make it work at the end.

11:21

Ian

11:21 PM

Okay, that file is different, let me see if I can get it to work.

11:23

Ian

11:23 PM

In the original script this line fails because the permissions are root and non-root:

cp $PROJECT_DIR/docker/deployment.Dockerfile $PROJECT_DIR/$BUILD_DIR

Oct 18, 2022 (14 months ago)

Ian

12:51 AM

$ docker image ls | grep typesense
typesense/typesense               nightly                          b6ffb22b8f1c   6 minutes ago    822MB
typesense/typesense-development   nightly                          e960b42ed3e4   17 minutes ago   5.17GB

12:51

Ian

12:51 AM

$ git diff --cached
diff --git a/docker-build.sh b/docker-build.sh
index 059afaa..e69e84b 100755
--- a/docker-build.sh
+++ b/docker-build.sh
@@ -29,7 +29,7 @@ if [[ "$@" == *"--depclean"* ]]; then
 fi
 
 
-TYPESENSE_DEV_IMAGE="typesense-development:27-JUN-2022-1"
+TYPESENSE_DEV_IMAGE="typesense-development:nightly"
 ARCH_NAME="amd64"
 
 if [[ "$@" == *"--graviton2"* ]]; then

Jason

12:52 AM

Yeah that should be changes needed… Did this nightly image work when you use it with docker run?

Ian

12:53 AM

No seems to be same problem.

Jason

12:53 AM

😞

Ian

12:53 AM

Jason

12:53 AM

Kishore Nallan Any thoughts here?

Ian

12:53 AM

I'm suspicious that some cruft is left in that long set of steps.

Jason

12:54 AM

Just to confirm, the compilation process finished successfully without any errors yeah?

Ian

12:54 AM

TYPESENSE_VERSION=nightly ./docker-build.sh --build-deploy-image --create-binary --clean

Jason

12:54 AM

What were the last few lines of the output of that command?

Ian

12:55 AM

Creating deployment image for Typesense nightly server ...
+ cp /home/ian/workspace/laspilitas-project/typesense/docker/deployment.Dockerfile /home/ian/workspace/laspilitas-project/typesense/build-Linux
+ docker build --file /home/ian/workspace/laspilitas-project/typesense/build-Linux/deployment.Dockerfile --tag typesense/typesense:nightly /home/ian/workspace/laspilitas-project/typesense/build-Linux
Sending build context to Docker daemon  435.4MB
Step 1/7 : FROM ubuntu:16.04
 ---> b6f507652425
Step 2/7 : RUN apt-get -y update && apt-get -y install ca-certificates
 ---> Using cache
 ---> fcdd8e825033
Step 3/7 : RUN mkdir -p /opt
 ---> Using cache
 ---> 4f5e1feca84b
Step 4/7 : COPY typesense-server /opt
 ---> e35dad4a35cd
Step 5/7 : RUN chmod +x /opt/typesense-server
 ---> Running in b6e9a1f0d73e
Removing intermediate container b6e9a1f0d73e
 ---> 2d20f833c3f6
Step 6/7 : EXPOSE 8108
 ---> Running in 4819a975c579
Removing intermediate container 4819a975c579
 ---> 07f38aafca69
Step 7/7 : ENTRYPOINT ["/opt/typesense-server"]
 ---> Running in fd683bf4b494
Removing intermediate container fd683bf4b494
 ---> b6ffb22b8f1c
Successfully built b6ffb22b8f1c
Successfully tagged typesense/typesense:nightly
+ [[ --build-deploy-image --create-binary --clean == *\-\-\p\a\c\k\a\g\e\-\b\i\n\a\r\y* ]]
+ echo 'Done... quitting.'
Done... quitting.