Posts made by wouter

wouter

Trying to use the ubuntu image on the VOXL results in error for me:

voxl:~$ docker run arm64v8/ubuntu:22.04 echo 1

Unable to find image 'arm64v8/ubuntu:22.04' locally
 

Pulling repository docker.io/arm64v8/ubuntu

Error: Status 410 trying to pull repository arm64v8/ubuntu: "<html>\r\n<head><title>410 Gone</title></head>\r\n<body>\r\n<center><h1>410 Gone</h1></center>\r\n<hr><center>openresty</center>\r\n</body>\r\n</html>\r\n"

Looking at the documentation, the helloworld image is used (https://docs.modalai.com/docker-on-voxl/#running-a-docker-image).

Pulling this image on the VOXL (docker pull helloworld) results in the same error

Error: Status 410 trying to pull repository library/helloworld: "<html>\r\n<head><title>410 Gone</title></head>\r\n<body>\r\n<center><h1>410 Gone</h1></center>\r\n<hr><center>openresty</center>\r\n</body>\r\n</html>\r\n"

It seems that an old version of docker is the cause. Is it possible to upgrade docker?

wouter

@Alex-Gardner Thank for your reply, could you maybe look at my question I still have?

wouter

Thanks, this makes a bit more clear.

I tried running your command, but it returns an error. I tried cat'ing test? and that stalls.

yocto:~$ echo "test" > /run/mpa/vvpx4_sys_status/request && cat /run/mpa/vvpx4_sys_status/test
cat: /run/mpa/vvpx4_sys_status/test: No such file or directory
yocto:~$ ls -alh /run/mpa/vvpx4_sys_status/
total 4.0K
drwxr-xr-x.  2 root root 100 Jun  7 04:33 .
drwxr-xr-x. 12 root root 260 Jan  1  1970 ..
-rw-r--r--.  1 root root 185 Jan  1  1970 info
prw-r--r--.  1 root root   0 Jun  7 04:33 request
prw-r--r--.  1 root root   0 Jun  7 04:33 test?
yocto:~$ cat /run/mpa/vvpx4_sys_status/test?

wouter

Hi,
I like to query the data from /run/mpa/vvpx4_sys_status from inside a docker container.
I'm running docker with -v /run/mpa/:/run/mpa:rw, so I can see /run/mpa/vvpx4_sys_status
Is there a way to read the data without using modal_pipe_client?
I tried cat /run/mpa/vvpx4_sys_status/request but that just stalls.
I'm running dotnet in the container and tried using NamedPipeClientStream, but that eventually gives a time-out.