CHBMB

This is something you'd have to ask the Medusa team, I genuinely don't think any of this could be attributed to the docker container environment.

Look at the forum settings, make sure signatures are switched on and you'll see a link in my sig to Docker Run Command. That's what we need to see.

Have you mapped that location to a docker mount like /tv or /movies or /remote mount Post your docker run command

Not without more context. Need to see what you're doing to generate that error message. To clarify, is it the docker service that won't start? Or a docker container? If it's the former, you need to post diagnostics, if it's the latter then some more info on the container etc

Oh I got the joke, meant to quote the person above, although my offer stands@BRiT I'd love to work with you! Sent from my Mi A1 using Tapatalk

It's an enormous amount of work to log each change, it's just not feasible. @BRiT Unless you want to volunteer to do ours matey? 😜

The syncing process with the v4 Emby and v4.0.x plugin is significantly faster than on the older releases. Sent from my Mi A1 using Tapatalk

The path for Sonarr is wrong, it's probably also going to be /tv It needs to be the path that the Sonarr container is using container side not host (Unraid) side.

Unfortunately those are the system logs, whereas the information that might be helpful are the docker run command and the docker logs. Info on how to find these can be found in the docker faq or in my signature.

Yes for my TLD, then Cnames for my subdomains and a wildcard cert from LE.

Namecheap is my default go to provider. Using Cloudflare as DNS

Store the appdata on a SSD rather than a HDD. Don't spin down the disks you use to store data on. Sent from my Mi A1 using Tapatalk

Correct, it's based on Nginx Sent from my Mi A1 using Tapatalk

Without some more detailed information on how to reproduce, or logs, or docker run command, you may be waiting a while......

Tried restarting the container since then? Sent from my Mi A1 using Tapatalk

I don't use Sabnzbd, but is there somewhere in it's webui to configure log location and/or size? If so /config would be an appropriate location Sent from my Mi A1 using Tapatalk

Because that is not the intention of how docker containers are run. They're meant to be run as independent micro-services. We experimented with containers with multiple services in it before and it was a complete fuster-cluck. But as you're an expert critic of what makes a well put together docker container fork it and make your own.

That's why we asked for help testing......

My telephone line is at the top of a telegraph pole. I can see it from where I'm sitting in my office and also from my lounge. I have guns.... Just saying 😜

One easy way to do it, power down the server with your appdata on (which should all be on a cache disk, not sure I'd try this with a BTRFS pool) and mount it in the new server with unassigned devices, then copy from disk to array. (Make sure you copy rather than move!! And I'd probably back it up on server 1 before doing this as well, can't be too careful.)

They do, it's part of the filesystem.

But it isn't a variable. I'm not being arsey, just want to ensure you understand the file structure before you start copying stuff to /mnt/chris1259/appdata and find yourself wondering where it all went when you restarted your server, as I think it would be in RAM and "poof" disappear.

Huh, it should be /mnt/user/appdata

Easiest solution is to just copy across your /appdata share and then repull the containers from Docker hub. Just make sure your volume mounts are still valid on the second server. You could also copy across the XML files from your flash to have easy access to the templates as you've configured them. Essentially there are only two points in the docker ecosystem on Unraid where the data is custom to your install. Appdata and XML files. Personally I'd just copy across the appdata and recreate the containers manually so you can still leverage CA for reinstalling/management.

I don't personally use ZFS, but I'm going to put these links here as some of you guys might be interested. Greg KH has given a statement on ZFS in the v5 kernels which I suspect (although have no absolute proof) is what Unraid v6.7.0 will be using. https://www.phoronix.com/scan.php?page=news_item&px=ZFS-On-Linux-5.0-Problem https://github.com/zfsonlinux/zfs/issues/8259