And that's why. They're on different networks. The 172 address can and will change and are issued dynamically when in bridge. By design and no options in bridge mode.
Have you cleared your browser history (specifically cookies). Also, if you haven't updated CA (Apps) in quite a while you should update it before clearing the cookies
I'd reboot and see what happens. If there's still a problem, then post a new set of diagnostics (there's a ton of repeating errors logged, possibly all related, but hard to determine what exactly happened)
Would also be worthwhile to update to 6.10.3
That would be a challenge since those aren't aren't post arguments but rather additional commands you're executing via the docker run command when it's being created initially
I would add a custom start script as /boot/config/plugins/ca.update.applications/scripts/starting/Nextcloud
Where Nextcloud is the name of the container exactly.
Yes, write speed when writing a file. Reads are not affected at all and will happen at the native speed of the drive (subject to bandwidth considerations etc)
Worst case, delete /config/plugins/community.applications and /config/plugins/community.applications.plg and reboot
Then reinstall either via the URL in the OP or if on 6.11 just by going to the apps tab.
If the reinstall doesn't work, the show me the entire output of what appears so that I can put it into context
Docker containers can and will change their internal IP address (the 172.... address) If you're referencing 172... then you do not want to do that. You reference the HOST IP address and the applicable port #
Unraid has no "power saving" on the CPU unless you install the sleep plugin (which you don't have)
It would be worthwhile to not run your memory at an overclock (3000MT/s) The memory you purchased F4-3000C15-8GVR is actually 2133. Disabled XMP / AMP is the BIOS and also run a memtest from the boot menu for a minimum of a pass - If you're booting the OS via UEFI, you will need to temporarily switch to Legacy boot in order to run the test
The entire docker FAQ. Not a huge issue in the greater scheme of things. After all, no one ever actually looks in there when they have problems.... 😜 (Told you I'd never let you forget it)
Your flash drive is being mounted as read only due to corruption. Toss it into a separate computer and run the file system checks on it
If problems continue replace it with a quality drive (kingston)
There was a report that the container had a trojan embedded in it. It was removed from Apps a couple days ago as a precaution pending a full investigation (this weekend)
There's both more or less identical.
Main difference is that if you reference /mnt/user (this is preferred) then the system will follow all the share's settings for cache pool usage, split levels, etc. Directly specifying a disk (or a pool) limits the files to be specifically on that disk and will disregard any share settings
If you're using Portainer to manage, install etc compose files then what happens if you use Portainer to make the changes?
Not saying that there's an issue per se, but it really simplifies things to use one method to manage the containers you install via that method and not another one (docker tab) that has no idea about how the containers were installed etc