Apologies in advance if this topic has already been covered. I can’t find any posts about udev issues since PR #1206 has been merged in though.
- Host OS Version:
- Supervisor Version:
- Device type:
CTI Spacely TX2 (BETA)
- Using Ubuntu 16.04 as the base of the container
- Running a single container on the device
Here is my issue: I am trying to set specific device rules inside the solo container that is running. I just can’t seem to find the right way to do it. I have followed what seem like the most recent steps in this PR: PR1209 (that I believe has been merged into master at this point), but I can’t seem to get the rules to run.
Here is my exact workflow:
- Download .img file from Balena Cloud
- Download config file from Balena Cloud
- Add udev rules to the config file under
os/udevRulesas specified in the steps in PR1209
- Update .img using the command
balena os configure my_image.img --app my_ap_name --config ./my_config.json --version 2.29.2
- Burn image to SD card using Balena Etcher
- Flash to device
The device flashes just fine, but my udev rules still are not seeming to take effect. When I run
balena config read --type spacely-tx2 to read the config from the SD card I don’t see any os related keys. This leads me to believe that I am not updating the .img using the config file properly, but I am not sure of anything at this point.
Thanks in advance for anything you all can help with! I love using Balena and this is really the first issue that has stumped me. I appreciate whatever you can do.