I believe I know the issue! http://kong:8000 is only going to work if the Archon container is in the same Docker network as the Supabase container. But if you’re using the local AI stack separately than Archon that won’t be the case. You could add Archon into the local-ai network (or whatever your local AI network is) or point to host.docker.internal instead of kong
localai does indeed create localai_default and Archon connects to bridge but I just add Archon to the localai_default in Portainer and then disconnect it from bridge…just won’t take the creds…connects to kong I see the error on both sides. I am convinced it’s going to be something stupid on my part.
Just perplexing how it just won’t take a cred other things will in the same container
OK…finally
I used the anon key and then I opened up all the permissions on the table. Not advisable outside your own office but it finally did it. Once I did that I thought perhaps it would take the Service key but…nope “you are not allowed access”.
Last but not least I was having a really hard time getting the permissions accepted on my Linux image in the db so I massaged everything with my .env and docker file and copied the entire localai directory structure to a shared drive and popped back into Windows and copied over. I had to change a few minor things but got the whole stack of 24 containers up and running smoothly. I then got the db permissions set and connected at long last.
Not sure why it wants the anon key but definitely will not except service key.
1 Like
That’s super strange, glad you got it working though!