[BUG] Unable to run docker on Ubuntu Linux - Illegal instruction (core dumped)

[nikhilno1]

Description

Tried to run the docker command as mentioned in README, but getting error.

$ docker run -e GRADIO_SERVER_NAME=0.0.0.0 -e GRADIO_SERVER_PORT=7860 -v /mnt/data/ktem_app_data:/app/ktem_app_data -p 7860:7860 -it --rm ghcr.io/cinnamon/kotaemon:main-full
/app/launch.sh: 20: ollama: not found
[nltk_data] Downloading package punkt_tab to
[nltk_data]     /usr/local/lib/python3.10/site-
[nltk_data]     packages/llama_index/core/_static/nltk_cache...
[nltk_data]   Unzipping tokenizers/punkt_tab.zip.
Illegal instruction (core dumped)
exit status 132

(.venv) nikhil@db-server:~/projects/kotaemon$ cat /etc/issue
Ubuntu 24.04.2 LTS \n \l

Reproduction steps

1. Run the docker command as given in README
2. See error

Screenshots

![DESCRIPTION](LINK.png)

Logs

Browsers

No response

OS

Linux

Additional information

No response

[taprosoft]

Might be relevant. Could have some issue with older Xeon CPUs with lesser instruction set.
#257 (comment)

[nikhilno1]

Thanks. Although this processor was released 4 years ago. Not sure if that can be called as old. Anyways, this looks to be the end of my journey then.

[rickenbb]

Thanks. Although this processor was released 4 years ago. Not sure if that can be called as old. Anyways, this looks to be the end of my journey then.

Hi! FYI in case you are running virtualization... I figured out a workaround for this issue.
E.g. in Proxmox you can set a "processor type". When I set this to "x86-64-v4" it worked for me.

[nikhilno1]

Awesome. Worked for me too. Thanks so much Benjamin.

…

On Mon, Mar 10, 2025, 10:19 PM Benjamin Rickenbacher < ***@***.***> wrote: Thanks. Although this processor was released 4 years ago. Not sure if that can be called as old. Anyways, this looks to be the end of my journey then. Hi! FYI in case you are running virtualization... I figured out a workaround for this issue. E.g. in Proxmox you can set a "processor type". When I set this to "x86-64-v4" it worked for me. — Reply to this email directly, view it on GitHub <#689 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC4XG6QNMF6J2X2NHKTB6A32TW7BNAVCNFSM6AAAAABYQPWVHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJRGIZDEMRZHE> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: rickenbb]*rickenbb* left a comment (Cinnamon/kotaemon#689) <#689 (comment)> Thanks. Although this processor was released 4 years ago. Not sure if that can be called as old. Anyways, this looks to be the end of my journey then. Hi! FYI in case you are running virtualization... I figured out a workaround for this issue. E.g. in Proxmox you can set a "processor type". When I set this to "x86-64-v4" it worked for me. — Reply to this email directly, view it on GitHub <#689 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC4XG6QNMF6J2X2NHKTB6A32TW7BNAVCNFSM6AAAAABYQPWVHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJRGIZDEMRZHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>