Hello, unfortunately there is no video resource on this, but let us know if anything is unclear and we should be able to improve it or provide support. As far as NTFS goes, I am afraid we do not support it at the moment, can you try reformatting the USB into some other filesystem (e.g. ext4)
No worries, it can be quite a bit overwhelming in the beginning, but its actually quite simple. This page has all the steps, but let me try and explain them in a way that is hopefully more clear.
So the first two sections (balenaOS kernel support and Preparing the container) ensure that everything is correctly setup for you to be able to mount your USB correctly. You have already made it past the first step by reformatting the USB stick, the next step would be to modify your local docker-compose.yml and Dockerfile as described in Preparing the container and then balena push your changes to your application.
Once this is setup you will be able to mount the USB stick in your container. You can run something like mount -t <fstype> -o rw -L <device-label> <mount-point> where fstype will be ext4, mount-point should be a folder you create for the stick and device-label is the label of you USB stick (you can find that out by running lsblk -f from the hostOS). Once you are done with the USB stick you can unmount it by simply running umount <mount-point>.
This should be all you need to get going. The issue with this method is that you have to manually mount and unmount the USB stick every time you plug it in and out. The idea described in the section called Automounting/unmounting with UDev rules is to setup the hostOS to automatically run your mount and unmount commands every time something is plugged or unplugged from the USB port. Let me know if you need any more help with that, the idea is to simply create these udev rules (contained in the usb.rules) that run some mount and unmount scripts (which should contain the commands you ran manually in the previous step) every time a device is connected/disconnected.
So you already have a wifi-repeater-master service (no docker-compose.yml, just a Dockerfile) and you want to add another container (docker-deluge-master) also without a docker-compose.yml. You want them both to run on your devices, correct?
Put the docker-deluge-master directory and the wifi-repeater-master into the same folder with nothing else.
Remove wifi-repeater-master/docker-compose.yml
Add the following docker-compose.yml to the same directory as docker-deluge-master and wifi-repeater-master (I’m assuming the wifi repeater code is from here):