Looking at this guide:

https://docs.modalai.com/voxl-m500-user-guide-using-vio/

I seem to be able to run some of the commands, but not all of them:

voxl:/etc$ cd modalai/
voxl:/etc/modalai$ ls
docker-autorun-script.sh         voxl-imu-server.conf
extrinsics.conf                  voxl-mavlink-server.conf
modalai.png                      voxl-qvio-server.conf
tag_locations.conf               voxl-streamer.conf
voxl-camera-server.conf          voxl-tag-detector.conf
voxl-dfs-server.conf             voxl-tflite-server.conf
voxl-factory-bundle-version.txt  voxl-vision-px4.conf
voxl:/etc/modalai$ vi voxl-qvio-server.conf 
voxl:/etc/modalai$ systemctl status voxl-qvio-server
● voxl-qvio-server.service - voxl-qvio-server
   Loaded: loaded (/usr/bin/voxl-qvio-server; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2023-01-19 15:07:45 UTC; 4min 26s ago
 Main PID: 4322 (voxl-qvio-serve)
   CGroup: /system.slice/voxl-qvio-server.service
           └─4322 /usr/bin/voxl-qvio-server

Jan 19 15:07:45 apq8096 voxl-qvio-server[4322]: LNX_8096 supported? 1
Jan 19 15:07:45 apq8096 voxl-qvio-server[4322]: LNX_IA64 supported? 1
Jan 19 15:07:45 apq8096 voxl-qvio-server[4322]: WINDOWS supported? 0
Jan 19 15:07:45 apq8096 voxl-qvio-server[4322]: AR ERROR: arFileOpen(): Fail...l
Jan 19 15:07:45 apq8096 voxl-qvio-server[4322]: FASTCV: fcvAvailableHardware...x
Jan 19 15:07:45 apq8096 voxl-qvio-server[4322]: mempool cur block size 30720...0
Jan 19 15:07:45 apq8096 voxl-qvio-server[4322]: Please ignore the error abou...^
Jan 19 15:07:45 apq8096 voxl-qvio-server[4322]: It's an optional file, and s...r
Jan 19 15:07:45 apq8096 voxl-qvio-server[4322]: waiting for imu
Jan 19 15:07:45 apq8096 voxl-qvio-server[4322]: waiting for cam
Hint: Some lines were ellipsized, use -l to show in full.
voxl:/etc/modalai$ voxl-qvio-server-configure
bash: voxl-qvio-server-configure: command not found
voxl:/etc/modalai$ 

voxl-qvio-server-configure in particular isn't available, but the service seems to be running anyway, however voxl-qvio-client also doesn't work so it's hard to verify that it really is indeed the case of it working - looking for a way to fly without GPS initialization indoors

@Steve-Sager said in Issues with Docker, and WiFi connection:

The WiFi on the aircraft will not connect to the local guest WiFi network (while in station mode) even after following the steps in the instructions

Have you tried \ as an escape char before the _ or space of your wifi name in order to get it to connect (when running the adb shell voxl-wifi station <name> <password> command)

@Steve-Sager said in Issues with Docker, and WiFi connection:

@Cristian-Adam Yes the wifi ID name I'm trying to connect to has spaces, but to get around that you can just put a underscore where the space would be.

I'm not understanding if this means you were able to get the wifi working via a work-around or not, I needed to escape the underscore as well

does your wifi that it can't connect to have any special characters in the name or password that need to be escaped? (like spaces)

Trying to follow this ros_environment guide

that came about from the mavros page indicating docker is on the drone/needed to run stuff, but docker-on-voxl seems to be out of date, so figuring out how to run docker on voxl is being challenging - loading voxl-docker support seems like it worked correctly however -

unable to run

docker load -i roskinetic-xenial_v1_0.tgz

it errors out with:

ERRO[0511] Handler for POST /v1.21/images/load returned error: Untar re-exec error: exit status 1: output: write /482b910388d5d604cb01d5c10b07ab3dcf243a34d4f539749fe9249671a41856/layer.tar: no space left on device 
ERRO[0511] HTTP Error                                    err=Untar re-exec error: exit status 1: output: write /482b910388d5d604cb01d5c10b07ab3dcf243a34d4f539749fe9249671a41856/layer.tar: no space left on device statusCode=500

I have tried running this from the /data directory where there is space, but I am not sure how to re-map where docker expands images into or if I can (should) use the SD card slot for this instead

There seems to be room on the disk, just not where it's being run from:

voxl:/data$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       2.8G  1.8G  939M  66% /
devtmpfs        1.8G     0  1.8G   0% /dev
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           1.9G   17M  1.9G   1% /run
tmpfs           1.9G     0  1.9G   0% /sys/fs/cgroup
tmpfs           1.9G  8.0K  1.9G   1% /var/volatile
/dev/sde12       12M  4.1M  7.4M  36% /dsp
/dev/sda2       2.2M   80K  2.0M   4% /persist
/dev/sde11       95M   33M   63M  35% /firmware
/dev/sda3        58M   40K   57M   1% /cache
/dev/sda9        15G  620M   14G   5% /data
tmpfs           378M     0  378M   0% /run/user/0