[stop useless backups]

On 9/8/2021 at 9:15 PM, ljm42 said:

Alright, I think I've got this figured out. The system is not happy that we are running commands manually but let's try this:

 

/etc/rc.d/rc.flash_backup stop
git -C /boot rm --cached /boot/config/plugins/rclone/.rclone.conf
git -C /boot commit -m "remove .rclone.conf"
git -C /boot push
/etc/rc.d/rc.flash_backup start

 

This should prevent the .rclone.conf file from being tracked.

 

My system was suffering from this condition. I could not execute this fix quoted above due to file locks. I was able to resolve the problem by de-activating the flash backup in the MyServers plug in, rebooting, and re-activating the flash backup. I hope this fix sticks. 🙂

[AVAHI or Bonjour Across VLAN's]

Since this was the first result in a Google search when I was looking for a solution, I will post my solution here. I created an MDNS reflector with a  Docker container to reflect between my secure LAN , IOT -VLAN2, and Guest -VLAN3 networks. Change the specifics to fit your situation. 
 

1- Create docker networks for the VLANs (one time setup in Unraid terminal):

   docker network create --driver macvlan --subnet 192.168.2.0/24 --gateway 192.168.2.1 --opt parent=eth0.2 vlan2

   docker network create --driver macvlan --subnet 192.168.3.0/24 --gateway 192.168.3.1 --opt parent=eth0.3 vlan3 

 

2- Create docker container:

    Name:Avahi  (name is used in Post Arguments later)

    Repository:flungo/avahi

    Network Type:Custom:br0

    Fixed IP address:192.168.1.20

 

   Docker Variables:

      REFLECTOR_ENABLE_REFLECTOR

         Key:REFLECTOR_ENABLE_REFLECTOR

         Value:yes

 

   Docker Post Arguments: (ADVANCED VIEW)

      ; docker network connect vlan2 Avahi --ip 192.168.2.20; docker network connect vlan3 Avahi --ip 192.168.3.20

[I cannot save the settings of CPU Pinning Docker]

I am having the same issue on v6.9.1 on CA installed containers.  If I attempt to change the container CPU pinning via the dashboard page the changes do not save. If I change the container advanced settings the changes do save however, they are out of sync with the settings displayed on the dashboard page. When the container is running, It appears that the dashboard page settings take precedence. The work around I found was to delete and then re-add the container.