Closed leiless closed 7 months ago
Might related: https://github.com/supabase/supabase/pull/13632
# Uncomment to use Big Query backend for analytics
# volumes:
# - type: bind
# source: ${PWD}/gcloud.json
# target: /opt/app/rel/logflare/bin/gcloud.json
# read_only: true
# Uncomment to use Big Query backend for analytics
# GOOGLE_PROJECT_ID: ${GOOGLE_PROJECT_ID}
# GOOGLE_PROJECT_NUMBER: ${GOOGLE_PROJECT_NUMBER}
https://github.com/Logflare/logflare/blob/v1.4.0/config/runtime.exs#L192-L211
Hi @leiless
Thanks for opening! I cannot reproduce this on MacOS (orbstack) or Linux (podman). Can you make sure that any volumes are removed and that the lines you mention are commented? Potentially podman has an issue with the comments in the file but, as I cannot repro, I am not sure if this is the case
Closing as this has not had a follow up but, if the issue still occurs, let us know and we can reopen!
I have encountered the same issue, and I found the underlying problem and a workaround.
I'm using the command podman-compose -f docker/docker-compose.yml up analytics
(it is the same if I'm having the whole stack up); from the terminal output, I see it was running the below command (truncated for brevity)
podman create --name=supabase-analytics ........ -e LOGFLARE_SINGLE_TENANT=True .... supabase/logflare:1.4.0
the important bits being it was running the command using "True" as the LOGFLARE_SINGLE_TENANT
parameter value even though in the yml file it is lowercase true
.
But in logflare, it was actually being compared as a string, and since "True" != "true", the condition fall through and tries to use google cloud stuff instead of postgres
The "workaround" is directly use the string "true"
instead of the implicit boolean true
for those specific variables, i.e. in docker-compose.yml
, under "environment" for "analytics":
LOGFLARE_SINGLE_TENANT: "true"
podman-compose -v
:podman-compose version: 1.0.6 ['podman', '--version', ''] using podman version: 4.9.2 podman-compose version 1.0.6 podman --version podman version 4.9.2 exit code: 0
Bug report
Describe the bug
Run self-hosted supabase with podman 3.4.4, and the
supabase-analytics
is failed to start.To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Podman logs
Note the cause:
(File.Error) could not read file "gcloud.json": no such file or directory
System information