I have a DVB-T device I want to use within a docker app.
My problem is that the device requires a firmware file placed at /lib/firmware.
This path is Read Only in scale.
How can I get around this?
With a VM.
1 Like
Thank you for quick answer. But I would like it to be within apps/docker is that not possible or do you just prefer VM?
It’s possible, it’s not advised.
The root file system can be remounted as rw, but it’s easy to shoot yourself in the foot by doing that. And when you do, you’re going to have a harder time getting help.
TrueNAS is not a Linux distro, it’s a package of tuned software marketed as appliance software.
You CAN tinker with it, but when you do so you’re on your own. This is fine for advanced users, less so for newcomers. It comes down to being able to make an informed choice about it.
1 Like
In this particular instance I would rather use the DVB-T tuner with a STB appliance, and give the appliance access to a share on the NAS.
How do you remount the filesystem as rw?
I only need to copy one file to /lib/firmware. I do understand that the file i properbly lost when upgradeing my nas software. But if its only one file I think I can mange that.
Can you tell the system to look for the driver in another location?
like /home/username/lib/firmware
Solution found. But is not recommend to use in a production enviroment.
make Writable:
sudo /usr/sbin/zfs set readonly=off boot-pool/ROOT/24.10.2/usr
do your edit
sudo cp ~/dvb-demod-si2168-b40-01.fw /usr/lib/firmware
make Readonly again:
sudo /usr/sbin/zfs set readonly=on boot-pool/ROOT/24.10.2/usr
1 Like