Kilrah

Nope, you have to wipe it and recreate on the new drive.
Image is easy to move, folder can't be moved as it makes use of filesystem featrues that won't survive a simple copy. 
 
Also it seems the drive you want it on is zfs, folder on zfs drives is known to be problematic and break often/cause server crashes. Switch back to image if you want your Docker system on a zfs drive.

qemu-img can't resize a vmdk, would need to convert or use vmware to resize. 
Maybe best to download the qcow2 version (labelled for proxmox) or raw img version instead.

Weil es einfach nicht möglich ist.

Click on the gear next to the stack name.
 

https://docs.unraid.net/unraid-os/manual/shares/network-access/#access-permissions-at-share-level

Known 
 
 

Don't use 127.0.0.1, that's be the local address of the container. Use the actual network IP of where the service is running.

Diags are just after boot so don't show any error, but that looks like filesystem corruption, Check filesystem

If you used du it's simply inaccurate due to the way layers work, it'll end up counting the same thing many times over. 

If you want to use 9p you have to manually mount the share from command line or fstab.
NFS also needs some manual care... easiest is probably smb. 

See the support thread for that container, latest version is broken.

https://account.unraid.net/

Works just fine here with the registry container on bridge.
 

 
I do have it reverse proxied with SSL though.

Only if you could have a USB drive connected to it for the OS...
 
But what hardware maintenance do you need anyway? I just clean my sever once or twice a year. Most maintanance is software and you'll still need to do that.

You have Docker set to use a folder so that essentially reflects the used space on the drive your system share is on.

It gives that container its own IP on your network with all ports available as a result.

Reboot.

That's 8 years old, doubt you can still upgrade automatically.
I'd screenshot the main page with disk assignments, backup the entire flash drive, redo an install with the creator and restore the config folder, but I'd also expect some stuff to be broken afterwards, so much has changed since.
 
Also make sure your hardware is able to run the current version, particularly RAM.

You can set it to primary Cache, secondary array, mover goes array->cache, shutdown the docker service and run the mover.

SMART log does show uncorrectable errors at the locations unraid couldn't read, so yeah that's a bad disk.
What's on the parity drive is indeed just garbage that means nothing in an array with >2 drives.

Copy the license file from a previous usb backup into the config folder, redownload it from your email link, or from unraid connect if you linked with that

What?!
 
But yeah, reboot is the official solution. Usually doing a manual unmount of the stale mountpoint in the terminal works to avoid it. If you do a 'mount' to list mounts you should see it in /mnt/disks and be able to 'umount' it.

The data is mirrored (maybe not necessarily 1:1 on the exact same drive bits?) and metadata will differ since zfs knows it is supposed to be a 2-drive pool, is able to know a disk is missing and which. If you put that in the array the single data drive might mount but as a degraded 2-drive pool.

It has nothing to do with the machine, only the usb drive. The one you originally used would have been blacklisted when you transferred the license, but new ones shouldn't.
Possible your location could be selling fake Sandisk sticks, it's the brand that's the most counterfeited in the field. Try another brand.

Looks like you have the Mover Tuning plugin installed, it being not/improperly configured is a common cause of "mover not working" issues. Check settings/remove it if you don't need it.