Open anilnatha opened 11 months ago
After some trial and error, I've made progress in getting my local environment set up.
I'm now at the point where running the command make backend
produces a docker error that I'm investigating
✔ Container vip-dev-env-proxy-proxy-1 Created 0.0s
Error response from daemon: Ports are not available: exposing port TCP 127.0.0.1:443 -> 0.0.0.0:0: failed to connect to /var/run/com.docker.vmnetd.sock: is vmnetd running?: dial unix /var/run/com.docker.vmnetd.sock: connect: no such file or directory
ERROR ==> /Applications/Docker.app/Contents/Resources/bin/docker-compose,--project-name,vip-dev-env-proxy,--file,/Users/anatha/.local/share/vip/lando/proxy/proxy-0.yml,--file,/Users/anatha/.local/share/vip/lando/proxy/proxy-1.yml,--file,/Users/anatha/.local/share/vip/lando/proxy/proxy-2.yml,--file,/Users/anatha/.local/share/vip/lando/proxy/proxy-3.yml,--file,/Users/anatha/.local/share/vip/lando/proxy/proxy-4.yml,up,--detach,--remove-orphans,proxy failed with exit code 1
Thanks to this post, I was able to resolve the issue I was encountering with Docker Desktop.
Able to run codebase locally; however, encountered some issues that will need to be addressed as we proceed. Hoping the SMD/JPL Dev team will be able to provide insights regarding these issues
@anilnatha is now analysing how to integrate our code to the SMD code base by copying their repository.
@anilnatha is making progress on that ticket and in parallel prepares questions for the SMD team.
@anilnatha is blocked because the SMD documentation is partly unavailable.
@anilnatha also prepared questions for the SMD team.
We need to go through the process of setting up our local environment so that we can try running the SMD codebase locally.
Information related to set up local development system is located: