-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
Analytics docker image unhealthy when self-hosting due to migration issue (sources
not found)
#28348
Comments
@Akash187 Can you help me in this issue please as we are stuck in this problem since a week now. The analytics image is just unable to start and we are getting errors while starting the images |
@encima Any updates please |
@raman04-byte for me it is working fine on my Macbook CLI v1.187.10. |
I am not using CLI Create the image for the amd/Linux and run it. You can use this |
Are you using self-hosted version? |
@raman04-byte no update in the few hours since you opened the issue :) Then please ensure
|
I am on latest commit for master and have cleared all the cache (even reinstalled the docker) and all the images are the latest one Images with tags also: ![]() and yes I am using latest version of Supabase ![]() |
I am using Self-Hosting with docker by cloning the repo and than compose up |
These are all the steps we are doing I did not want to pull the studio image from the docker so we did one modification in the docker-compose.yml file and using a script we ran it ![]() docker-compose.yml:
docker-compose2.yml:
and script we are using is this
and after all that we are facing this issue ![]() |
|
The issue is not with the studio we are not pulling it is with the supabase-analytics container which is not able to run properly. Here are the docker ps and docker logs of supabase-analytics container
|
sources
not found)
Thanks for this, this looks like an issue with migrating the analytics schema for Logflare. To check:
Also, it looks like you are missing some containers ( |
how to check credentials for the Postgres db and also how to check Any docs so that I can get those credentials and share to you |
The postgres credentials are in your Please do not share those credentials here (or anywhere else). This is only to confirm that the connection information is correct |
I can share the .env file because I just clone the repo and started pulling that so no sensitive information is there |
Use the credentials in that file to confirm that you can connect to your Postgres container. If you cannot, delete the postgres container and volumes and run it again (note: you will lose data) |
Postgres does not support HTTP connections so you cannot use a browser to connect. Try using a SQL GUI (i.e. pgAdmin) or psql (documentation in the comment above) If you still have issues, you might be better off asking in the Discord channel |
Let me test with pgAdmin and will get back to you |
ok, so you have connected. that is good. are you connected as the user |
OK, logflare is using the |
Correct. It is doing that because it cannot connect to the database (see the logs you posted).
|
Use the credentials from your env file. Check the docs https://supabase.com/docs/guides/self-hosting for more info |
I am only using credentials of env file |
Also if I do not use linux/amd64 to build it than it is working fine and there is no issue with the any images so far. So there is some issue with the analytics linux/amd64 image |
You will need the credentials of the |
Will |
docker (and others) supports emulation, yes. using the |
Let me give it a try than I will get back to you |
I can not use other than |
@encima any other solution? |
afraid not. We can test this with a Linux build but the current workaround would be to run it under a different architecture |
Bug report
Describe the bug
Well I am trying to deploy the supabase localhost to the Red Hat Linux server and I am not able to start the container it shows that analytics can't start
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Expected behavior
It should start normally
Screenshots
System information
Additional context
Well I have macOS and I am building the image for the Red Hat Linux server and I am failing to do so
The text was updated successfully, but these errors were encountered: