ERROR: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get “http://%2Fvar%2Frun%2Fdocker.sock/_ping”: dial unix /var/run/docker.sock: connect: permission denied
The thread you linked culminates in a pull request that supports Bookworm fully.
The prereqs script should eliminate the need to install packages manually. Its name is slightly misleading, as it works for several common distros and not just Ubuntu.
Don’t use that script or manually install a bunch of packages. Just use Tools/environment_install/install-prereqs-ubuntu.sh immediately after cloning the repository on a fresh OS install. Works perfectly and even updates submodules.
OK, installing that ‘arm-none-eabi’ package is peanuts, but for instance, I am not sure, if you even have ‘git’ on a clean Debian installation? Ubuntu or LM might have those packages installed per default, but Debian keeps things simple from the start.
./install-prereqs-ubuntu.sh: line 449: //Tools/completion/completion.bash: No such file or directory
Then a Logout — login and the terminal shows that
bash: //Tools/completion/completion.bash: No such file or directory
kalle@debian:~$ cd ardupilot
kalle@debian:~/ardupilot$ /.waf configure --board revo-mini
bash: /.waf: No such file or directory
kalle@debian:~/ardupilot$
~/ardupilot$ ./waf configure --board revo-mini
Setting top to : /home/kalle/ardupilot
Setting out to : /home/kalle/ardupilot/build
Autoconfiguration : enabled
Checking for program ‘python’ : /usr/bin/python3
Checking for python version >= 3.6.9 : 3.11.2
Setting board to : revo-mini
Using toolchain : arm-none-eabi Could not find the program [‘arm-none-eabi-ar’] (complete log in /home/kalle/ardupilot/build/config.log)
kalle@debian:~/ardupilot$
it is just that your are in a VM and probably not use some interactive user so the .profile isn’t loaded. That is our toolchain isn’t into your PATH. install gcc-arm-none-eabi from apt repo create a diff against our tests and can be totally broken …
I just tested on a fresh Bookworm container, and everything worked perfectly, including configuring and building for the Revo board you’re using.
It appears you elected not to make ArduPilot the default venv for Python (recommended), and it looks like you also decided not to install the STM32 toolchain, if I’m reading your install log correctly. At a minimum, you need the STM32 toolchain.
If you want the smoothest experience, you really ought to say “y” to all prompts (many default to “n” if you just press enter).
You can opt out of the default venv, but then (on the most recent Debian-based distros) you must execute this command prior to building: source ~/venv-ardupilot/bin/activate
If you don’t see a prompt beginning with venv-ardupilot, things won’t go well: (venv-ardupilot) yuri@apbookworm:~/ardupilot$
To exit the venv (and build environment), you can use deactivate at any time.
Hey guys, thank you so much indeed for your input!
Wanted to add, I am an Ubuntu user since 12 years and I consider myself knowledgeable on Debian/Ubuntu. This is NOT any sort of container or VM, it’s my daily use Ubuntu 20.04.6 LTS PC where this
happened.
Github is installed
I successfully cloned Ardupilot
The required dependencies installed without any problems
It would appear (as the error message I got says) you’d need a Docker key instead of username/password to proceed from there.
BUILD SUMMARY
Build directory: /home/kalle/ardupilot/build/revo-mini
Target Text (B) Data (B) BSS (B) Total Flash Used (B) Free Flash (B) External Flash Used (B)
bin/arduplane 881364 2460 128692 883824 99208 Not Applicable
Build commands will be stored in build/revo-mini/compile_commands.json
‘plane’ finished successfully (2m29.547s)
(venv-ardupilot) kalle@debian:~/ardupilot$