Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: compose crashs docker desktop. #1846

Closed
mailmehao opened this issue Dec 7, 2023 · 3 comments
Closed

[Bug]: compose crashs docker desktop. #1846

mailmehao opened this issue Dec 7, 2023 · 3 comments
Labels
area: backend Related to backend functionality or under the /backend directory bug Something isn't working Stale

Comments

@mailmehao
Copy link

What happened?

esxi8, ubuntu220401, 20CPUs/16GRAM/200G.
I git quivr to local, cp .env.example to .env, uncomment OLLAMA_API_BASE_URL, add host.docker.internal to /etc/hosts file.
have docker and ollama installed in advance. "docker compose pull" seems OK.
"docker compose -f docker-compose-ollama.yml up --build" cmd crashs docker desktop.
supabase-rest keeps going errors out.

Relevant log output

supabase-vector                 | 2023-12-07T10:45:34.422794Z  INFO source{component_kind="source" component_id=docker_host component_type=docker_logs component_name=docker_host}: vector::internal_events::docker_logs: Started watching for container logs. container_id=d33cadec893f7e4f850cecf94dc26a4bdd2a87a050712e6d6dde2531a33c8284
supabase-db                     | 
supabase-db                     | PostgreSQL Database directory appears to contain a database; Skipping initialization
supabase-db                     | 
supabase-vector                 | 2023-12-07T10:45:34.776247Z ERROR transform{component_kind="transform" component_id=db_logs component_type=remap component_name=db_logs}: vector::internal_events::remap: Mapping failed with event. error="function call error for \"upcase\" at (476:516): expected string, got null" error_type="conversion_failed" stage="processing" internal_log_rate_limit=true
supabase-vector                 | 2023-12-07T10:45:34.776459Z ERROR transform{component_kind="transform" component_id=db_logs component_type=remap component_name=db_logs}: vector::internal_events::remap: Internal log [Mapping failed with event.] is being rate limited.
supabase-vector                 | 2023-12-07T10:45:35.950523Z  WARN sink{component_kind="sink" component_id=logflare_db component_type=http component_name=logflare_db}:request{request_id=0}:http: vector::internal_events::http_client: HTTP error. error=error trying to connect: dns error: failed to lookup address information: Name does not resolve error_type="request_failed" stage="processing" internal_log_rate_limit=true
supabase-vector                 | 2023-12-07T10:45:35.979342Z  WARN sink{component_kind="sink" component_id=logflare_db component_type=http component_name=logflare_db}:request{request_id=0}: vector::sinks::util::retries: Retrying after error. error=Failed to make HTTP(S) request: error trying to connect: dns error: failed to lookup address information: Name does not resolve internal_log_rate_limit=true
supabase-vector                 | 2023-12-07T10:45:37.058603Z  WARN sink{component_kind="sink" component_id=logflare_db component_type=http component_name=logflare_db}:request{request_id=0}:http: vector::internal_events::http_client: Internal log [HTTP error.] is being rate limited.
supabase-vector                 | 2023-12-07T10:45:37.058717Z  WARN sink{component_kind="sink" component_id=logflare_db component_type=http component_name=logflare_db}:request{request_id=0}: vector::sinks::util::retries: Internal log [Retrying after error.] is being rate limited.
supabase-imgproxy               | INFO    [2023-12-07T10:45:39Z] Started /health  request_id=-2L1PjqZ7P1Zfz52xGVI4 method=GET client_ip=127.0.0.1
supabase-imgproxy               | INFO    [2023-12-07T10:45:39Z] Completed in 16.378811ms /health  request_id=-2L1PjqZ7P1Zfz52xGVI4 method=GET status=200 client_ip=127.0.0.1
supabase-vector                 | 2023-12-07T10:45:40.600588Z  INFO source{component_kind="source" component_id=docker_host component_type=docker_logs component_name=docker_host}: vector::internal_events::docker_logs: Started watching for container logs. container_id=3f3255289d96406601033640fcbc21d0c45746f53a186a4638aa0522ee373844
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: An error ocurred when loading the schema cache
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: {"code":"58P01","details":null,"hint":null,"message":"could not access file \"$libdir/wrappers-0.1.19\": No such file or directory"}
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Starting PostgREST 11.2.2...
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Attempting to connect to the database...
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Connection successful
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Config reloaded
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: An error ocurred when loading the schema cache
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: {"code":"58P01","details":null,"hint":null,"message":"could not access file \"$libdir/wrappers-0.1.19\": No such file or directory"}
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Starting PostgREST 11.2.2...
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Attempting to connect to the database...
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Connection successful
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Config reloaded
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: An error ocurred when loading the schema cache
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: {"code":"58P01","details":null,"hint":null,"message":"could not access file \"$libdir/wrappers-0.1.19\": No such file or directory"}
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Starting PostgREST 11.2.2...
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Attempting to connect to the database...
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Connection successful
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Config reloaded
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: An error ocurred when loading the schema cache
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: {"code":"58P01","details":null,"hint":null,"message":"could not access file \"$libdir/wrappers-0.1.19\": No such file or directory"}
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Starting PostgREST 11.2.2...
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Attempting to connect to the database...
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Connection successful
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Config reloaded
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: An error ocurred when loading the schema cache
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: {"code":"58P01","details":null,"hint":null,"message":"could not access file \"$libdir/wrappers-0.1.19\": No such file or directory"}
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Starting PostgREST 11.2.2...
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Attempting to connect to the database...
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Connection successful
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Config reloaded
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: An error ocurred when loading the schema cache
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: {"code":"58P01","details":null,"hint":null,"message":"could not access file \"$libdir/wrappers-0.1.19\": No such file or directory"}
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Starting PostgREST 11.2.2...
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Attempting to connect to the database...
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Connection successful
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Config reloaded
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: An error ocurred when loading the schema cache
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: {"code":"58P01","details":null,"hint":null,"message":"could not access file \"$libdir/wrappers-0.1.19\": No such file or directory"}
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Starting PostgREST 11.2.2...
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Attempting to connect to the database...
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Connection successful
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Config reloaded
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: An error ocurred when loading the schema cache
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: {"code":"58P01","details":null,"hint":null,"message":"could not access file \"$libdir/wrappers-0.1.19\": No such file or directory"}
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Starting PostgREST 11.2.2...
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Attempting to connect to the database...
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Connection successful
supabase-rest                   | 07/Dec/2023:10:50:07 +0000: Config reloaded
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: An error ocurred when loading the schema cache
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: {"code":"58P01","details":null,"hint":null,"message":"could not access file \"$libdir/wrappers-0.1.19\": No such file or directory"}
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Starting PostgREST 11.2.2...
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Attempting to connect to the database...
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Connection successful
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Config reloaded
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: An error ocurred when loading the schema cache
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: {"code":"58P01","details":null,"hint":null,"message":"could not access file \"$libdir/wrappers-0.1.19\": No such file or directory"}
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Starting PostgREST 11.2.2...
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Attempting to connect to the database...
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Connection successful
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Config reloaded
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: An error ocurred when loading the schema cache
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: {"code":"58P01","details":null,"hint":null,"message":"could not access file \"$libdir/wrappers-0.1.19\": No such file or directory"}
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Starting PostgREST 11.2.2...
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Attempting to connect to the database...
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Connection successful
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Config reloaded
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: An error ocurred when loading the schema cache
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: {"code":"58P01","details":null,"hint":null,"message":"could not access file \"$libdir/wrappers-0.1.19\": No such file or directory"}
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Starting PostgREST 11.2.2...
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Attempting to connect to the database...
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Connection successful
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Config reloaded
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: An error ocurred when loading the schema cache
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: {"code":"58P01","details":null,"hint":null,"message":"could not access file \"$libdir/wrappers-0.1.19\": No such file or directory"}
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Starting PostgREST 11.2.2...
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Attempting to connect to the database...
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Connection successful
supabase-rest                   | 07/Dec/2023:10:50:08 +0000: Config reloaded
Gracefully stopping... (press Ctrl+C again to force)
unexpected EOF

Twitter / LinkedIn details

No response

@mailmehao mailmehao added the bug Something isn't working label Dec 7, 2023
Copy link

dosubot bot commented Dec 7, 2023

🤖

Hello @mailmehao,

I'm Dosu, a bot designed to help with issues just like the one you're experiencing. I'm here to assist you in finding bugs, answering your questions, and guiding you on how to become a contributor. While you're waiting for a human maintainer, I'm here to help you. Let's get to resolving your issue!

The error message "could not access file "$libdir/wrappers-0.1.19": No such file or directory" suggests that the PostgreSQL extension required by your application is not installed or not accessible. This error is not directly related to Docker or Ollama, but to the PostgreSQL setup in your Docker container.

The extension seems to be required by the supabase-rest service, which uses the postgrest/postgrest:v11.2.2 image. This image is based on the official PostgreSQL image, but it doesn't include all PostgreSQL extensions.

To solve this issue, you need to create a custom Docker image based on postgrest/postgrest:v11.2.2 and install the required PostgreSQL extension in it. Here is an example of how you can do it:

# Dockerfile
FROM postgrest/postgrest:v11.2.2

# Install required PostgreSQL extension
RUN apt-get update && apt-get install -y postgresql-13-wrappers

Then, you need to build this Docker image and use it in your docker-compose-ollama.yml file:

# docker-compose-ollama.yml
services:
  rest:
    container_name: supabase-rest
    build:
      context: .
      dockerfile: Dockerfile
    # ...

Please replace postgresql-13-wrappers with the correct package name for the required PostgreSQL extension. If the extension is not available in the official Ubuntu repositories, you may need to add a third-party repository or compile the extension from source.

As for the role of the supabase-rest service within the Quivr application, I wasn't able to find specific information within the repository. It's possible that this information is available elsewhere or I may have missed it. If you have more details about the role of this service, it could help in further troubleshooting.

I hope this helps! If you have any more questions or need further clarification, feel free to ask.

Source

Sources


This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

@dosubot dosubot bot added the area: backend Related to backend functionality or under the /backend directory label Dec 7, 2023
StanGirard pushed a commit that referenced this issue Dec 10, 2023
# Description

I tried to use the Quivr with the docker-compose-ollama.yml option but
the docker compose build crashed with the following messages:

`{"code":"58P01","details":null,"hint":null,"message":"could not access
file \"$libdir/wrappers-0.1.19\": No such file or directory"}`

After a quick search I saw that the issue was related to the
supabase/postgres image and after a quick compare with the default
docker-compose.yml i saw that it uses a newer version for the
supabase/postgres image and when i tried the newer version with the
docker-compose-ollama.yml the errors stopped and the app works fine.

Relative issues: #1846 #1822 #1850
@tsensei
Copy link

tsensei commented Dec 13, 2023

@StanGirard Can you look into this please? It is also initiating a loop while doing docker compose up with the development compose file

Copy link
Contributor

Thanks for your contributions, we'll be closing this issue as it has gone stale. Feel free to reopen if you'd like to continue the discussion.

@github-actions github-actions bot added the Stale label Jan 13, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 18, 2024
@dosubot dosubot bot mentioned this issue Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: backend Related to backend functionality or under the /backend directory bug Something isn't working Stale
Projects
None yet
Development

No branches or pull requests

2 participants