supabase-vector (vector.yml)

[EasternIndustries-IT]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

Setting up new supabase instance in ubuntu 22.04 using the most recent docker-compose I get an error
supabase-vector | 2024-05-08T19:02:48.897393Z INFO vector::app: Loading configs. paths=["etc/vector/vector.yml"]
looking deeper it looks like it created a folder in /volumes/logs/vector.yml/
on my other docker instances in windows it creates a file vector.yml

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

Clear docker containers, images , prune images, then run docker-compose up from a directory with only a compose file in it.

Expected behavior

no errors

Screenshots

System information

• OS: ubuntu 22.04

Other information

Even if I can get it to work by copying a vector.yml from my other instance i get supabase_admin has no password assigned upon docker-compose up

[encima]

Hey there, this is a docker issue that seems to be getting more common!
Is your Ubuntu machine running on ARM or x86?

If you provide the valid path, I would also tear everything down, remove cached volumes and make sure you are starting from scratch. Let us know how that goes!

[EasternIndustries-IT]

Hey there, this is a docker issue that seems to be getting more common! Is your Ubuntu machine running on ARM or x86?

If you provide the valid path, I would also tear everything down, remove cached volumes and make sure you are starting from scratch. Let us know how that goes!

I am using an ubuntu 22.04 x64 on and intel processor. Everything is updated to the latest as of 05.06.2024.

[encima]

yep, this will happen when you the processor is x64 as the build is different than the image architecture. You can use buildx to cross compile it as well if you like.

See this image here for the same.

[EasternIndustries-IT]

yep, this will happen when you the processor is x64 as the build is different than the image architecture. You can use buildx to cross compile it as well if you like.

See this image here for the same.

I am not quite sure on how to do that with a docker compose file. I tried adding a platform: linux/x86_64 but i still get the same issue. I'm also unsure of what platform this is built on.

This error also happens with vector.yml on windows 11 which is also x64 but ubuntu 20.04.06 wsl.

[jasper-at-windswept]

I have the same issue running NixOS 24.05.

What doesn't make sense is i got this to work with no issues, but then I reinstalled my system and now I get this problem described at the top.

*Edit
I re-setup the whole instance from scratch and it worked without any issues. Except this one which someone found a solution to.
https://github.com/orgs/supabase/discussions/19603