CHBMB

Try again, I've deleted it from our repository, Sent from my Mi A1 using Tapatalk

Then just rename it .sample Sent from my Mi A1 using Tapatalk

On mobile at the moment. Post the contents of the quassel-web.subfolder.conf file Sent from my Mi A1 using Tapatalk

Thanks man, much appreciated, it wasn't a dig at you at all. But I think now we have a degree of separation it should be easier to support for both of us. You can have as many notices telling people where to get support, they still ignore them, I know that. Sent from my Mi A1 using Tapatalk

That may well be the case, but the matter stands.

Don't take this the wrong way, but I don't need the hint..... Like I said, I know what I'm doing here. Sent from my Mi A1 using Tapatalk

You're missing a very very important point here. Containers are immutable, the container I run, is the same as the container you run, which is the same as the container @OOmatrixOO is running. I think we both know he wouldn't know where to start with that link, and Ubuntu doesn't necessarily translate well to an Alpine docker container. Instead I remoted in and just pulled a fresh container, typed the commands as I set out and it worked fine.

PM sent, I dunno what you're doing, but something ain't right....

@OOmatrixOO Have you got this working now?

Docker DNS as far as I know works fine as long as you create a custom docker network and run all the containers on that. It's what we use in the letsencrypt reverse proxy configs. Did a diff on that working config versus the default Unraid one. Essentially these are the missing components on Unraid CONFIG_NETFILTER_XT_MATCH_IPVS: missing CONFIG_CGROUP_HUGETLB: missing CONFIG_NET_CLS_CGROUP: missing CONFIG_CGROUP_NET_PRIO: missing CONFIG_IP_VS: missing CONFIG_IP_VS_NFCT: missing CONFIG_IP_VS_PROTO_TCP: missing CONFIG_IP_VS_PROTO_UDP: missing CONFIG_IP_VS_RR: missing CONFIG_EXT4_FS_SECURITY: missing CONFIG_IPVLAN: missing CONFIG_DUMMY: missing CONFIG_NF_NAT_FTP: missing CONFIG_NF_CONNTRACK_FTP: missing CONFIG_AUFS_FS: missing Which ones of these are important I couldn't say. But it does illustrate nicely that things aren't just as simple as flicking a switch to enable a single kernel module. I activated the top one in that build I made earlier in the this thread. How essential the others are to your requirements I don't know, and I'm reluctant to f**k with stuff I don't understand at a kernel level on the Nvidia build.

There's no point in elevating with sudo in your example as by definition when you run a touch command in the container the file is owned by root. The purpose of sudo -u abc is to run the command as the abc user, so sudo touch and touch are essentially the same thing. Sent from my Mi A1 using Tapatalk

FWIW I know it'll work as I was the one that added sudo to the container to allow us to run commands as the specified user from the command line so it would be possible to run occ as the same user that Nextcloud runs under. Sent from my Mi A1 using Tapatalk

Do you mind? I've written the solution and he's hitting a forum bug, not an issue with the code I've written. I do kind of know what I'm doing here..... Test for yourself TYPE sudo -u abc touch /config/test In the container and guarantee it'll work. Sent from my Mi A1 using Tapatalk

I know that sudo -u abc works the issue is the damned forum sometimes adds invisible characters to text copied and pasted from it. Sent from my Mi A1 using Tapatalk

I wouldn't do that as Nextcloud runs as abc Sent from my Mi A1 using Tapatalk

Or report it upstream to IPS I mean, it's a bug in their software.....

Type the command in manually, don't copy/paste I think this is probably the forum bug causing an issue.

What is your nextcloud container called? By default it's nextcloud Linux is case sensitive so have you changed anything to caps or renamed it in any way? Sent from my Mi A1 using Tapatalk

Right now run these commands: docker exec -it nextcloud bash sudo -u abc touch /config/log/nextcloud.log chmod 777 /config/log/nextcloud.log then edit config.php in /mnt/cache/appdata/nextcloud/www/config/config.php and include these two lines 'loglevel' => 1, 'logfile' => '/config/log/nextcloud.log', and restart your container. Now as /config is really /mnt/cache/appdata/nextcloud and remember that /mnt/user/ = array disks and cache disk and /mnt/user0 = array disks without cache disk your log file for nextcloud will be in /mnt/user/appdata/nextcloud/log/ and called nextcloud.log Because you had the log directory partially on the array there was every chance that if that was where the nextcloud.log file was it would continue to write to the array even with just the config.php changes. By removing that rogue /mnt/user0/appdata/nextcloud directory and setting use cache disk to prefer it will stop that from happening again

Then the container is working and on the right version. You tested the settings in Sonarr/Radarr?

And @OOmatrixOO stop trying to do two fixes synchronously, you'll complicate matters more and you're making changes to things you don't understand. As I said change Use cache disk to prefer.

Well for whatever reason you DO have the logs directory on your array as /mnt/user0/ is the array minus the cache disk. Apologies, typo in that command rm -rf /mnt/user0/appdata/nextcloud

Actually that shows there is part of you log file on the array. rm -rm /mnt/user0/appdata/nextcloud Will remove it. Probably need to check your appdata share to ensure it's set to prefer cache disk.

v6.7.0rc1-swarm.zip Here's a version of v6.7.0rc1 with the swarm patch applied. The check config script will still show it as missing the above two modules but they are included, but the script checks the contents of /usr/src/linux-4.19.43-Unraid/.config which I haven't changed as that would require unpacking bzroot. Instead I applied the patch above and just recreated bzmodules and bzfirmware The proof will be if it works or not. v6.7.0rc1-swarm.zip

There are two parameters that need changing IP_VS NETFILTER_XT_MATCH_IPVS