KluthR

What about posting some more details? At least the entered source???

Does no one use IPv6 inside Unraids docker? Could someone do a ping test from inside a container to a public server and observe if some "address unreachable" occur? I still need to retest with a native portainer install. Somehow I got a feeling that this is an Unraid thing...

No, currently not. But you could place a file with the command „docker start ClamAV“ somewhere and set is as post-run script.

The plugin is actually using the delay from the docker page: https://github.com/Commifreak/unraid-appdata.backup/blob/f5bfd73ed69afe0a7fb22707e11881d91708baf1/src/include/ABHelper.php#L263

In current .10 release I also see permanent DHCPD6 renew messages, didnt remember the exact term, hold on… dhcpcd[1128]: eth0: requesting DHCPv6 information every ten secs. But maybe its because I habe only Stateful RA enabled router?

Same issue here. Unraid does not pick up the latest prefix from RA. This dynamic prefix shit for private customers is a pain...

„Group“ field inside container specific settings.

It seems that something is messing with the files. Some other „thing“ that would do that? Mover? best way is to share your debug log.

@Revan335 its all described inside restore page except for „one file“. Either all or nothing. Its not selectable to only restore one file.

The start order is used for stop, backup, start. If you put both in one group, both get stopped, then backed up and then started like the group order is. So: yes, that would be your solution

New observings: Its not happening with bridge network interface. See https://forums.docker.com/t/occasional-ping-issues-over-ipv6/140296/2?u=rkluth @ich777 You also have IPv6 experiences with Unraids docker. Did you ever came accros such issue?

The order is effective for both modes as the container lost gets „sorted“ once when starting the backup.

But the log above that field is visible? No recent reboot or anything?

now.

Yea. Just checked. The plugins chmod runs after post-run. Will change that in next release

Check settings. Whats inside allowed appdata source paths? Is the volume in question maybe "external" and therefore excluded? Some of your containers excluding /mnt which leads to empty zips..? Point to the backup and restore all XMLs and appdatas. Use Previous apps to install all containers. Currently you need some manual work. Another check here: I bet this container is inside of a group?

Could you please upload a debug log and share its ID?

Oops. Yes, not CA related Could someone move it for me?

Interesting. Is there something special about /mnt/user/unraid_backup ? Whats happening if you run "mkdir /mnt/user/unraid_backup/appdata_backup/test"?

Feels more and more like a general v6 docker issue. docker and IPv6 are not the best friends. There are several issues regrading v6.

Hey I migrated from an exclusive cmk appliance to the docker version to get rid of one physical system. However, I experience permanent occasional v6 smart piung issues with the container. I can observe this with ping6 from inside the cmk container. Every few minutes I get 100% packet loss, then back to normal etc. Unraid 6.12.8 Anyone with similar issues? The container is set up this way: docker run -d --name='checkmkk_empty' --net='eth0' --ip='192.168.178.29' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="NAS" -e HOST_CONTAINERNAME="checkmkk_empty" -e 'CMK_SITE_ID'='l22' -l net.unraid.docker.managed=dockerman -v '/mnt/ssd/appdata/checkmk_empty/sites':'/omd/sites':'rw' -v '/etc/localtime':'/etc/localtime':'ro' -v '/mnt/ssd/appdata/checkmk/backup':'/backup':'rw' --mac-address 02:00:00:00:00:29 --tmpfs /opt/omd/sites/l22/tmp:uid=1000,gid=1000 'checkmk/check-mk-cloud:2.2.0p23' Some ping pictures which show the v6 issue only within cmk container. HA container does not show such issues..? HA is set up the same way. docker is using macvtap bridge. Thanks in advance!

= should be == right?

I try to release an update within the next day.

There is none. The restore tab should be self explanatory.

Did anyone tested the fix