Hello
I’m setting up the meshery-cloud and facing some issues running it locally.OS : windows- wsl ubuntu As mentioned in the docs
Expose local cloud server: Run ngrok http --domain=allowing-poorly-wolf.ngrok-free.app 9876
I’ve done it as described, and ngrok is running fine. However, I got stuck at this step:
Start dependencies Postgres, Kratos, and Hydra. Build and run Layer5 Cloud Server. Access at http://localhost:9876
I wasn’t able to run make server-local as it is asking to download soda cli, I tried installing from https://gobuffalo.io/documentation/database/soda/, but still encountering the same issue.
$ make server-local Makefile:653: *** Dependency missing: 'soda'. Ensure 'soda' is installed and available in your 'PATH' - https://gobuffalo.io/documentation/database/soda/. Stop
Try executing this:export PATH=$PATH:/home/<your-username>/go/bin
Thanks @vishalvivekm , it solved that issue, I setup postgress in wsl and connected docker desktop with wsl.
Now I’m getting this issue, where the issue with meshery-net
Error response from daemon: network with name meshery-net already exists
Here is the complete errro log
$ PATH=$PATH:/home/kaif/go/bin make server-local (docker rm -f postgres) || true postgres docker network create meshery-net || true Error response from daemon: network with name meshery-net already exists docker run -d \ --network meshery-net \ --name postgres -e POSTGRES_PASSWORD=postgres -e POSTGRES_DB=meshery -p 5432:5432 postgres 37f5ecb8c94d095e212cdbe0c0f757ba0c639b697d3bcd6a8c80d1aaa9d3d996 docker: Error response from daemon: Ports are not available: exposing port TCP 0.0.0.0:5432 -> 0.0.0.0:0: listen tcp4 0.0.0.0:5432: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted. make: *** [Makefile:341: postgres] Error 125
Error response from daemon: network with name meshery-net already exists
I solved the above errror by colsing the docker network connectiondocker network rm meshery-net
But getting this now, I guess the problem is with the postgress server, I’ve faced some problems backthen.
$ PATH=$PATH:/home/kaif/go/bin make server-local
Can you share what’s the result of followingsudo lsof -i :5432 ?
We need to kill the process occupying the port 5432 before attempting to start the server.
The above command gives you pid of existing process using that port, if any.
Take that pid and kill it like this
sudo kill <pid>
Then attempt building make server-local
No its nothing, there is no process running refred to this port
I see @Md_Kaif_Ansari
Can you please share the result of the following;
sudo docker ps
sudo systemctl status postgresql
vishalvivekm:
@vishalvivekm
$ PATH=$PATH:/home/kaif/go/bin make server-local
$ sudo service postgresql status
Nov 25 09:07:34 LAPTOP-HESMK8AC systemd[1]: Starting postgresql.service - PostgreSQL RDBMS…
$ docker ps
As you can see this
Error response from daemon: No such container: postgres
So I stoped the wsl postgresql and continued with container of postgres running and vice versa.
But still I wasn’t able to run it
Lee
November 25, 2024, 12:18pm
9
meshery-net is not why the command is failing.
I will ask here again for public @Md_Kaif_Ansari : what’s the result for sudo netstat -tuln | grep 5432
here is the output
$ sudo netstat -tuln | grep 5432
This postgresql is runing in wsl
kill this process and restart your docker and then run again make server local
@Sudhanshu_Dasgupta As you said
I stop the postgresql server
$ sudo service postgresql stop
The service is inactive now
$ sudo service postgresql status
$ sudo netstat -tuln | grep 5432
After that when I run it again
$ PATH=$PATH:/home/kaif/go/bin make server-local
To confirm I dont have any container running, the postgresql server is also inactive
Hmm, try to change the port in makefile (i guess line 343) for now and then run. If it works don’t commit please.
No @Sudhanshu_Dasgupta , it doesn’t work eather
$ PATH=$PATH:/home/kaif/go/bin make server-local
@Md_Kaif_Ansari everything set?
yeah @Sudhanshu_Dasgupta ,
I did it into linux path /home/<repo_name>. it is working fine though with no issues. I’m just setting up database user for getting started.
Also thinking of write a complete proposed solution for it, under this thread that would be beneficial for other contributors to follow up with the error.
