Hi,
Hope You are all well.
I Tried to follow the instructions from this video but I think my configurattion is not right.
This the message I got :
[root@vmi2462371 /]# cd local-ai-packaged/
[root@vmi2462371 local-ai-packaged]# python3 start_services.py --profile cpu
Supabase repository already exists, updating...
Running: git pull
Already up to date.
Copying .env in root to .env in supabase/docker...
Checking SearXNG settings...
SearXNG settings.yml already exists at searxng/settings.yml
Generating SearXNG secret key...
Detected Linux/Unix platform, using standard sed command...
SearXNG secret key generated successfully.
Error checking Docker container: Command '['docker', 'ps', '--filter', 'name=searxng', '--format', '{{.Names}}']' returned non-zero exit status 1. - assuming first run
Stopping and removing existing containers for the unified project 'localai'...
Running: docker compose -p localai -f docker-compose.yml -f supabase/docker/docker-compose.yml down
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Traceback (most recent call last):
File "/local-ai-packaged/start_services.py", line 242, in <module>
main()
File "/local-ai-packaged/start_services.py", line 229, in main
stop_existing_containers()
File "/local-ai-packaged/start_services.py", line 52, in stop_existing_containers
run_command([
File "/local-ai-packaged/start_services.py", line 21, in run_command
subprocess.run(cmd, cwd=cwd, check=True)
File "/usr/lib64/python3.9/subprocess.py", line 528, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['docker', 'compose', '-p', 'localai', '-f', 'docker-compose.yml', '-f', 'supabase/docker/docker-compose.yml', 'down']' returned non-zero exit status 1.
I don’t know what to do.
Can you help me please ?
Thank you for your time.
Hi @BChrist,
I just think your docker is not running. Did you start the docker app/service?
Thanks.
I updated and enabled docker.
Now, one container is not healthy :
✔ Network localai_default Created 0.2s
✔ Volume "localai_db-config" Created 0.0s
✔ Container supabase-imgproxy Started 0.9s
✔ Container supabase-vector Healthy 6.5s
✔ Container supabase-db Healthy 73.8s
✘ Container supabase-analytics Error 79.3s
✔ Container supabase-kong Created 0.1s
✔ Container supabase-studio Created 0.1s
✔ Container supabase-pooler Created 0.1s
✔ Container supabase-edge-functions Created 0.0s
✔ Container supabase-meta Created 0.1s
✔ Container supabase-auth Created 0.1s
✔ Container realtime-dev.supabase-realtime Created 0.1s
✔ Container supabase-rest Created 0.1s
✔ Container supabase-storage Created 0.0s
dependency failed to start: container supabase-analytics is unhealthy
Traceback (most recent call last):
File "/local-ai-packaged/start_services.py", line 242, in <module>
main()
File "/local-ai-packaged/start_services.py", line 232, in main
start_supabase()
File "/local-ai-packaged/start_services.py", line 63, in start_supabase
run_command([
File "/local-ai-packaged/start_services.py", line 21, in run_command
subprocess.run(cmd, cwd=cwd, check=True)
File "/usr/lib64/python3.9/subprocess.py", line 528, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['docker', 'compose', '-p', 'localai', '-f', 'supabase/docker/docker-compose.yml', 'up', '-d']' returned non-zero exit status 1.
Thank you so much for your help.
Hm the erros does not say much 
Maybe the port 4000 in use by another application on your system?
PS: Please use code formatting for logs etc 
(I corrected it in your posts, to make it easier to read)
This is what I found
[root@vmi2462371 local-ai-packaged]# sudo ss -lntp | grep 4000
LISTEN 0 4096 0.0.0.0:4000 0.0.0.0:* users:(("docker-proxy",pid=182785,fd=7))
Thank you for your help.
I dont know what exactly this is but seems something internal from docker.
Maybe just restart the docker-service completely. If not working you can also change the port of analytics I guess in the docker-compose.yml (the first one (4001:4000 then).
But not sure if this works, when other services check on this port. Maybe not … needed to take then deeper in it.
PS: I am off for today. Looking into your replies tomorrow. good luck
I made a research on Google.
I reinstalled my VPS and I followed the instruction guide from the video and now everything is operational.
Thank you so much for your help and your time.
(You can close my post if you want)
1 Like
