[Bug]: Listing currently running containers failed. error=error trying to connect: Permission denied (os error 13)

What happened?

Listing currently running containers failed. error=error trying to connect: Permission denied (os error 13)

Relevant log output

✔ Container supabase-vector    Created                                                                                                                                                               0.0s 
 ✔ Container supabase-imgproxy  Created                                                                                                                                                               0.0s 
 ✔ Container redis              Created                                                                                                                                                               0.0s 
 ✔ Container worker             Created                                                                                                                                                               5.1s 
 ✔ Container beat               Recreated                                                                                                                                                             6.4s 
 ✔ Container backend-core       Recreated                                                                                                                                                             7.0s 
 ✔ Container flower             Recreated                                                                                                                                                             8.7s 
 ✔ Container web                Recreated                                                                                                                                                             3.5s 
Attaching to backend-core, beat, flower, realtime-dev.supabase-realtime, redis, supabase-analytics, supabase-auth, supabase-db, supabase-edge-functions, supabase-imgproxy, supabase-kong, supabase-meta, supabase-rest, supabase-storage, supabase-studio, supabase-vector, web, worker
supabase-imgproxy               | WARNING [2023-12-30T00:18:10Z] No keys defined, so signature checking is disabled 
supabase-imgproxy               | WARNING [2023-12-30T00:18:10Z] No salts defined, so signature checking is disabled 
supabase-imgproxy               | WARNING [2023-12-30T00:18:10Z] Exposing root via IMGPROXY_LOCAL_FILESYSTEM_ROOT is unsafe 
supabase-imgproxy               | INFO    [2023-12-30T00:18:10Z] Starting server at :5001 
redis                           | 1:C 30 Dec 2023 00:18:10.529 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis                           | 1:C 30 Dec 2023 00:18:10.529 * Redis version=7.2.3, bits=64, commit=00000000, modified=0, pid=1, just started
redis                           | 1:C 30 Dec 2023 00:18:10.529 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis                           | 1:M 30 Dec 2023 00:18:10.530 * monotonic clock: POSIX clock_gettime
redis                           | 1:M 30 Dec 2023 00:18:10.531 * Running mode=standalone, port=6379.
redis                           | 1:M 30 Dec 2023 00:18:10.531 * Server initialized
redis                           | 1:M 30 Dec 2023 00:18:10.532 * Loading RDB produced by version 7.2.3
redis                           | 1:M 30 Dec 2023 00:18:10.532 * RDB age 182 seconds
redis                           | 1:M 30 Dec 2023 00:18:10.532 * RDB memory usage when created 0.83 Mb
redis                           | 1:M 30 Dec 2023 00:18:10.532 * Done loading RDB, keys loaded: 0, keys expired: 0.
redis                           | 1:M 30 Dec 2023 00:18:10.532 * DB loaded from disk: 0.001 seconds
redis                           | 1:M 30 Dec 2023 00:18:10.532 * Ready to accept connections tcp
supabase-vector                 | 2023-12-30T00:18:10.637118Z  INFO vector::app: Internal log rate limit configured. internal_log_rate_secs=10
supabase-vector                 | 2023-12-30T00:18:10.637235Z  INFO vector::app: Log level is enabled. level="vector=info,codec=info,vrl=info,file_source=info,tower_limit=trace,rdkafka=info,buffers=info,lapin=info,kube=info"
supabase-vector                 | 2023-12-30T00:18:10.637280Z  INFO vector::app: Loading configs. paths=["etc/vector/vector.yml"]
supabase-vector                 | 2023-12-30T00:18:10.658781Z  WARN vector::config::loading: Transform "router._unmatched" has no consumers
supabase-vector                 | 2023-12-30T00:18:10.658955Z  INFO source{component_kind="source" component_id=docker_host component_type=docker_logs component_name=docker_host}: vector::sources::docker_logs: Capturing logs from now on. now=2023-12-30T00:18:10.658931087+00:00
supabase-vector                 | 2023-12-30T00:18:10.659004Z  INFO source{component_kind="source" component_id=docker_host component_type=docker_logs component_name=docker_host}: vector::sources::docker_logs: Listening to docker log events.
supabase-vector                 | 2023-12-30T00:18:10.795831Z  INFO vector::topology::running: Running healthchecks.
supabase-vector                 | 2023-12-30T00:18:10.796054Z  INFO vector::topology::builder: Healthcheck passed.
supabase-vector                 | 2023-12-30T00:18:10.796071Z  INFO vector::topology::builder: Healthcheck passed.
supabase-vector                 | 2023-12-30T00:18:10.796075Z  INFO vector::topology::builder: Healthcheck passed.
supabase-vector                 | 2023-12-30T00:18:10.796078Z  INFO vector::topology::builder: Healthcheck passed.
supabase-vector                 | 2023-12-30T00:18:10.796081Z  INFO vector::topology::builder: Healthcheck passed.
supabase-vector                 | 2023-12-30T00:18:10.796085Z  INFO vector::topology::builder: Healthcheck passed.
supabase-vector                 | 2023-12-30T00:18:10.796088Z  INFO vector::topology::builder: Healthcheck passed.
supabase-vector                 | 2023-12-30T00:18:10.796279Z  INFO vector: Vector has started. debug="false" version="0.28.1" arch="x86_64" revision="ff15924 2023-03-06"
supabase-vector                 | 2023-12-30T00:18:10.796366Z ERROR source{component_kind="source" component_id=docker_host component_type=docker_logs component_name=docker_host}: vector::sources::docker_logs: Listing currently running containers failed. error=error trying to connect: Permission denied (os error 13)
supabase-vector                 | 2023-12-30T00:18:10.805025Z  INFO vector::internal_events::api: API server running. address=0.0.0.0:9001 playground=http://0.0.0.0:9001/playground
supabase-vector                 | 2023-12-30T00:18:10.805217Z  INFO vector::app: All sources have finished.
supabase-vector                 | 2023-12-30T00:18:10.805270Z  INFO vector: Vector has stopped.
supabase-vector                 | 2023-12-30T00:18:10.808716Z  INFO vector::topology::running: Shutting down... Waiting on running components. remaining_components="logflare_db, logflare_realtime, logflare_kong, logflare_storage, logflare_auth, logflare_functions, logflare_rest" time_remaining="59 seconds left"
supabase-vector exited with code 0
dependency failed to start: container supabase-vector exited (0)

Twitter / LinkedIn details

No response

🤖

Hi @pradg73! 👋 I'm Dosu, a friendly bot here to assist while we wait for a human maintainer. I can help you resolve bugs, answer questions, and guide you in contributing to the repository. Rest assured, I'm here to ease your journey. Don't hesitate to ask for help!

The error message you're seeing, Listing currently running containers failed. error=error trying to connect: Permission denied (os error 13), is likely due to insufficient permissions for the supabase-vector container to access the Docker socket.

In the Quivr codebase, the supabase-vector container is responsible for storing and retrieving vector embeddings of documents in a Supabase database. It requires read-only access to the Docker socket to interact with the Docker daemon, as well as read-only access to its configuration file. These permissions are specified in the volume mappings in the Docker Compose file.

Here's what you can do to resolve this issue:

Ensure that the Docker socket file (/var/run/docker.sock) exists on your host machine. You can check this by running ls /var/run/docker.sock in your terminal.
Check the permissions of the Docker socket file. It should be readable by the user running the Docker daemon. You can check the permissions by running ls -l /var/run/docker.sock in your terminal.
If the Docker socket file is not readable by the Docker user, you can change the permissions by running sudo chmod a+r /var/run/docker.sock in your terminal. This command grants read permissions to all users.
Finally, restart your Docker containers by running docker-compose down followed by docker-compose up.

Please try these steps and let me know if the issue persists. If it does, it would be helpful to know more about your Docker setup, including the version of Docker you're using and the user you're running Docker as.

For more information on the supabase-vector container and its permissions, you can refer to the backend/vectorstore/supabase.py and docker-compose-no-frontend.dev.yml files in the Quivr repository.

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.

QuivrHQ / quivr