[bug] Problem with installation in docker

[mesheni]

And I encountered such a problem that not all containers are started, as a result, nothing works.

fastapi_app-1 | exec /app/scripts/entrypoint.sh: no such file or directory
fastapi_app-1 exited with code 1
celery_worker-1 | exec /app/scripts/entrypoint.sh: no such file or directory
celery_worker-1 exited with code 1

It doesn't find the script file, even though it is in this folder. I don't understand how to fix it

[choinek]

Did you use make install?

Please share all the commands you are running.

It seems like you built the image but did not mount the volume.

[mesheni]

Apparently, this command just didn't work for me. I thought it was only needed for automatic installation, so I immediately started entering commands for manual configuration.

I'll make a reservation right away that I did everything in the Windows environment.

I cloned the repository and moved to the downloaded folder. Entered this command:

cp .env.example .env

Then I executed this command:

docker-compose -f docker-compose.gpu.yml -p text-extract-api-gpu up --build

As a result, I created 3 images for ollama, redis, and for the program itself. The first two were running, and the third one gave an error that the script was not found.

[choinek]

Sorry, but we currently don't support the Windows platform; only Linux and macOS are supported. 😞

However, we’d love your help! Could you share more details or contribute to improving this setup? Are you using WSL2?

The issue might be related to volume mounting on your machine. Our current Docker configuration is tailored for development and isn’t yet production-ready - it's not building with files but relay on mounted files.

If you’re interested, feel free to mix a little bit with volumes inside docker-compose.gpu.yml

Please start with change:

    volumes: &appvolumes
      - .:/app

and

    volumes: *appvolumes

to

    volumes:
      - .:/app

(both of them same!)

But the problem might be related to some filesystem collisions.

[OwenGreeley]

Hello,
I encountered this same issue while trying to run the docker compose on Windows 10 with WSL2 installed. By changing the entry point to be ls -al /app/scripts/entrypoint.sh I confirmed that the script file was mapped to the docker image correctly. I then tried changing the entrypoint to bash /app/scripts/entrypoint.sh which gave me some odd errors regarding line endings. Based on that I determined that the actual problem was the line endings on entrypoint.sh script. By changing the script to use LF (bottom right in VScode), docker compose seems to run the script fine.

TL;DR: make sure scripts/entrypoint.sh uses LF line endings

[OwenGreeley]

I forgot to mention, I did make the change to volume that choinek mentioned above. Not sure if that matters

[archasek]

@mesheni were you able to get it to work?
@OwenGreeley did you change volumes paths?

edit: changing CRLF -> LF for entypoint.sh worked. no changes in volumes config needed