It's very easy to update docker images automatically with watchtower-updater. You only need to run this SSH command once. From portainer you will start watchtower which will scan all the images that are not stopped, update them if necessary and stop again. Do this every fortnight. It is not a good idea to update automatically because sometimes some containers need to be monitored.
Turn the router-wifi off and on
Everything is easy, find the answer to your questions yourself.
How do you do that? Maybe I can adapt your solutions to my needs (I move the dish with an arduino and I patched tvheadend to send commands to the arduino)
It's very simple, I have a group of channels that only the administrator of the TV server sees, that is, only me. This group of channels, which are very few, are each on a different satellite and are only managed by hdstar tuner because it can move the antenna. The rest of the channels are managed by the SAT>IP server, which cannot move the antenna. Since I can access many TV channels, I don't use any over-the-air EPG but rather a lot of internal EPG grabbers that tvheadend handles without problem.
Vbox TV Gateway tuners: Search the internet, they are IPTV tuners visible at home from DLNA ready to go. They allow you to download the playlist to tvheadend and decode if necessary. I have one 2xDVB-T/T2 for eight years and it still works perfectly with tvheadend. The website is: https://vboxcomm.com
Nobody has any experience with the geniatech/mygica hdstar?
It doesn't tune all channels on my LE x86_64, only partially. I only use geniatech/mygica hdstar to move the antenna rotor. To watch satellite TV I only use my old SAT>IP Digibit-R1 which cannot move the rotor. My advice is to use SAT>IP tuners, Enigma2 tuners, or Vbox TV Gateway tuners for LE.
you configured docker root dir to be in custom location?
Docker location is not important to me because I only use containers in which I am not interested in their location but only the location of the working directories that I define myself, and avoid specific docker volumes and networks. I can't avoid images but I don't use solitary images either and they are always associated with containers that create these images if necessary.
Can you live without knowing where the 'tar' command is? I do.
The answer is simple: YOUR DOCKER CONTAINERS WILL NOT SURVIVE THE FACTORY RESET.
You have a major problem. The strategy that I use from the beginning of using docker is:
1.- Saving everything related to docker in /storage/.config/dockers:
- Always use the SSH command line to launch new containers. This command line is saved in a script. For example: my launch command for docker tvheadend was saved in /storage/.config/dockers/9981-tvheadend.sh
- Forgetting to use kodi addons to launch new containers.
- All settings for each of my containers are in /storage/.config/dockers. For example: my tvheadend settings are in /storage/.config/dockers/tvheadend.
2.- Every three days I do an automated backup using cron on a different drive from the LibreELEC boot disk, deleting the backups older than 14 days (my old memory only remembers what I did yesterday and the day before yesterday). On the first day of each month I make an additional backup deleting the oldest ones of 3 months.
In this way I have no problem in recovering all or part of the system after a factory reset.
There are no magic solutions for your problem, perhaps saving the data directories of your containers before doing the factory reset may be the solution. Go thinking about using another method, good luck!
Sorry, I don't know what you're doing. Installing a WireGuard client is easy:
1.- Create a file /storage/.config/wireguard/WG-DDNS.configCode
[provider_wireguard] Type = WireGuard Name = WG-DDNS Host = <your-ddns-domain: luckyluke.duckdns.org> WireGuard.Address = <your-wg-ip: 10.10.20.4/32> WireGuard.PrivateKey = <your-wg-privatekey> WireGuard.PublicKey = <wg-public-key-for-wg-network> WireGuard.DNS = <dns-ip: 10.10.20.1> WireGuard.AllowedIPs = <allowed-ips: 0.0.0.0/0> WireGuard.EndpointPort = <wg-server-port: 51820> WireGuard.PersistentKeepalive = <wg-parameter: 25>
2.- Start up the WireGuard client service
3.- The output of the route command is similar toCode
x96air1:~ # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default * 0.0.0.0 U 0 0 0 wg0 10.10.10.0 * 255.255.255.0 U 0 0 0 ztc3quell2 10.10.20.0 * 255.255.255.0 U 0 0 0 wg0 172.17.0.0 * 255.255.0.0 U 0 0 0 docker0 192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0 192.168.1.1 * 255.255.255.255 UH 0 0 0 wlan0
The default route is wg0.
Sorry, if you are using an addon to install docker transmission, I don't use this and I can't help you. I have many docker services installed and they have all been installed from the SSH command console, and for this I have needed to study the installation parameters of each one of them, and above all, I always install the docker portainer service to manage the other containers to verify they are running finely, check the storage locations, and do checks within each container.
The most surprising thing about your case is that it seems that you cannot find the files related to your addon transmission. My recommendation is that you spend a little time studying docker and also install the docker portainer service to see what happens to your docker transmission service.
Stupid directories means they are useless and can be deleted
The download directory and the incomplete directory are the same and are in the root directory of your external disk. Do you want this?
If you want to be able to move the download directories to any site on your device from within the docker application you need to add the following parameters
this will create two new directories within the docker app that will link to your LE device
If i install docker i will get Qbittorrent?
This ssh command will install docker transmission:Code
docker run -d \ --name=9091-transmission \ --net=host \ -e PUID=0 \ -e PGID=0 \ -e TZ=Europe/Paris \ -e USER=transmission \ -e PASS=libreelec \ -p 9091:9091 \ -p 51413:51413 \ -p 51413:51413/udp \ -v /storage/.config/dockers/transmission/config:/config \ -v /storage/.config/dockers/transmission/downloads:/downloads \ -v /storage/.config/dockers/transmission/watch:/watch \ --restart unless-stopped \ linuxserver/transmission
it works very well and the CPU consumption is lower when idle than in the case of docker qbittorrent.
The configuration web is at http://<device-ip>:9091 (user: transmission, password: libreelec).
A couple of days ago I tried to install LE 10 over LE 9.2.6 on an x86_64 device and it was a disaster. I have a LE 9.2.6 that acts as a server in a small network of amlogic devices, some with CE 9.2.8 and S912 processor, and others with CE 19.2-Matrix_rc3 and S905X3 processor with which I had no problem updating to kodi 19.2-Matrix. My LE x86_64 server uses very few addons but many docker services and it was impossible for me to update from the LE 9.2.6 version without problems, in the end I had to do a reset to boot with LE 10.0.0 without warnings, but the problems did not end. I couldn't start the tvheadend docker server either, after half an hour I reinstalled LE 9.2.6 again and recovered the last backup, since then everything works fine again with LE 9.2.6. I will wait a few months to make a second attempt at installing LE 10.0.0.
docker create \ --name=oscam \ -e PUID=0 \ -e PGID=0 \ -e TZ=Europe/Paris \ --net=host \ -v /storage/.config/oscam:/config \ --restart unless-stopped \ linuxserver/oscam docker start oscam
the configuration directory is in /storage/.config/oscam and the web port is 8888. This works with any arm, arm64 and x86_64 architecture of any linux operating system, LibreELEC included. If you learn to compile oscam you will only learn to compile oscam, if you learn to handle docker you will learn to install many services on any device.
This addon 7.0-generic-special-oscam-7.0.101.zip is dated 2016 and therefore is too old. I think it is better to forget about this and use the docker linuxserver/oscam service which is up to date and works with any version of LibreELEC.
Go back to studying the documentation about docker, the --privileged parameter allows access to the hardware and therefore the audio output