Hi @wen.g.gong_9378
Thanks for reaching out and for using Agno! I’ve looped in the right engineers to help with your question. We usually respond within 48 hours, but if this is urgent, just let us know, and we’ll do our best to prioritize it.
Appreciate your patience—we’ll get back to you soon!
Hi @wen.g.gong_9378
It seems like the docker executable is not found.
Can you tell me what the response is if you run sudo systemctl status docker?
Also run
ls -l /var/run/docker.sock
ls -l $HOME/.docker/run/docker.sock
If it shows an error or is missing, Docker Desktop may not be correctly configured to create the socket.
You could also manually create the socket directory mkdir -p $HOME/.docker/run
Then restart Docker: systemctl --user restart docker-desktop
$ sudo systemctl status docker
Unit docker.service could not be found.
$ ls -l /var/run/docker.sock
ls: cannot access '/var/run/docker.sock': No such file or directory
$ ls -l $HOME/.docker/run/docker.sock
ls: cannot access '/home/papagame/.docker/run/docker.sock': No such file or directory
$ mkdir -p $HOME/.docker/run
$ systemctl --user restart docker-desktop
$ systemctl --user status docker-desktop
$ docker context ls
NAME TYPE DESCRIPTION DOCKER ENDPOINT KUBERNETES ENDPOINT ORCHESTRATOR
default moby Current DOCKER_HOST based configuration unix:///var/run/docker.sock
desktop-linux * moby Docker Desktop unix:///home/papagame/.docker/desktop/docker.sock
# docker.sock is at a different location,
$ ln -s $HOME/.docker/desktop/docker.sock $HOME/.docker/run/docker.sock
# ws still failed to launch,
# then I created sym-link as su
$ sudo ln -s $HOME/.docker/desktop/docker.sock /var/run/docker.sock
# then ws up error went away
$ ag ws up --env dev --infra docker --type image --force