Describe the bug
In a system where docker-ce was previously installed docker desktop sets up a builder called desktop-linux, but the default builder remains even if trying to completely remove docker from the system. Launchpad attempts to use that default builder even if the desktop-linux builder is set to the active builder. It gives an error 111 when it tries to download the containers because it attempts to connect to unix:///var/run/docker.sock instead of the unix:///home/user/.docker/desktop/docker.sock
A workaround is (as root) ln -s /home/user/.docker/desktop/docker.sock /var/run/docker.sock
Review logs and see error 111 immediately on start up
There is indication that it uses docker-ce in a split brain scenario where they are both installed (see the containers download, the volumes and networks are created, but it ultimately doesn't work on docker-ce as it doesn't build the containers because of a separate issue I didn't investigate as my goal was to get it to work with docker desktop)
Expected behavior
tari-launchpad should use the correct builder which is associated to docker-desktop and should be able to download and deploy the environment.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS & Version:
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy
6.5.0-21-generic # 21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Additional context
Add any other context about the problem here.
Describe the bug In a system where docker-ce was previously installed docker desktop sets up a builder called desktop-linux, but the default builder remains even if trying to completely remove docker from the system. Launchpad attempts to use that default builder even if the desktop-linux builder is set to the active builder. It gives an error 111 when it tries to download the containers because it attempts to connect to unix:///var/run/docker.sock instead of the unix:///home/user/.docker/desktop/docker.sock
A workaround is (as root) ln -s /home/user/.docker/desktop/docker.sock /var/run/docker.sock
To Reproduce Steps to reproduce the behavior:
There is indication that it uses docker-ce in a split brain scenario where they are both installed (see the containers download, the volumes and networks are created, but it ultimately doesn't work on docker-ce as it doesn't build the containers because of a separate issue I didn't investigate as my goal was to get it to work with docker desktop)
Expected behavior tari-launchpad should use the correct builder which is associated to docker-desktop and should be able to download and deploy the environment.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context Add any other context about the problem here.