All the other parts of this script seem to work, since the expected content was written to the files "/etc/ld.so.conf.d/picoscope.conf" and "/etc/udev/rules.d/95-pico.rules".
FROM node:12.19.0 AS base
RUN apt-get update
RUN apt-get install -y apt-transport-https apt-utils
RUN bash -c 'echo "deb https://labs.picotech.com/debian/ picoscope main" >/etc/apt/sources.list.d/picoscope.list'
RUN wget -O - https://labs.picotech.com/debian/dists/picoscope/Release.gpg.key | apt-key add -
# install DrDaq drivers
# This installation will fail in its post-installation script.
# The demanded drivers are being installed nevertheless.
# So to continue the build of this Dockerfile, status 0 is returned manually.
RUN apt-get install libusbdrdaq -y; exit 0
# manual reload of udev rules
RUN udevadm control --reload-rules && udevadm trigger
# ...
This workaround suits my needs for now, but I hope this flaw gets fixed soon.
Hope this helps anyone with a similiar problem.
in my WSL2 Ubuntu 18.04 and got the exact same error. Seems as if the problem occurs not only in docker containers but in other virtual environments as well...
I am facing the same issue, trying to make this run in Docker.
Why do I try running this in docker? The libraries from pico are not available in Arch linux repo, so I got the from the debian repo, converted them with `debtap` and installed them, but that didn't work. So next was to make this work in Ubuntu, which is supposed to be supported.
My docker file is the following and same error returns upon installing picoscope. I am not sure where to start investigating this though.
Containers usually do not mount `/dev/` path, thus there is no use of udevadm.
Just create a link to /bin/true during the installation, and remove it afterwards: