Niklas

Sonarr and Radarr do have support for proxy. Settings -> General

Just tried. Works here.

You're welcome. I'm glad I could help!

Something like this should work... 1. Open console to the mariadb container. 2. Type mysql followed by enter. If this gives you problems, try mysql --user=root You should see some information and help. Cursor should be at "MariaDB [(none)]> " 3. Paste the sql query: ALTER DATABASE nextcloud CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci; and press enter. Be sure to include the ; at the end. You should see something like "Query OK, 1 row affected". If you have named your database differently from standard install, change the "nextcloud" bit in the command to fit your config. 4. Type quit followed by enter. You can now close the console window. Run the other 2 commands in the console for the Nextcloud container. I think this should work. I started to use this container not that long ago so I don't need to do anything. It was done for me automatically when deploying this awesome container.

What MariaDB-container are you running? Updated? If MariaDB 10.3 or later you only need innodb_file_per_table=1 in custom.cnf Look at the instructions again: The instructions for MariaDB 10.3 OR LATER tells you: Make sure that you have innodb_file_per_table=1 in your /appdata/mariadb/custom.cnf It then tells you to "Continue at step 2 of the MySQL instructions." Step 2 of the MySQL instructions: Change your databases character set and collation: ALTER DATABASE nextcloud CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci; Edit: Look HERE to see where and how to enter this command. Edit: The following steps should be done in the console for the nextcloud container. Step 3: Set the mysql.utf8mb4 config to true in your config.php: sudo -u abc php /config/www/nextcloud/occ config:system:set mysql.utf8mb4 --type boolean --value="true" Step 4: Convert all existing tables to the new collation by running the repair step: sudo -u abc php /config/www/nextcloud/occ maintenance:repair I have changed the syntax for the console commands in step 3 and 4 to fit this container. MariaDB 10.3 and later does not have the FILE_FORMAT key. I guess barracuda is the default from 10.3 and up.

Changed to the new container built on alpine. A lot smaller now. Old one was Debian. Just change "Repository:" to mk0x/docker-clamav:alpine After that, delete the orphan image in your Docker container list.

I see the same "NOT notified" but I think we can disregard it. I saw it in other ClamAV containers too. No clear answer here: https://github.com/mko-x/docker-clamav/issues/12 But, as I said. It's only at startup and could probably be ignored.

Collabora is much better integrated too. I use it and had that problem but it went away with some recent update to the Collabora container. I use Traefik to proxy all traffic to my containers. All my containers that I need inet access to have their own sub-domains.

Yes. In several different containers. Check my earlier post about it and the one I use now. Edit: I got it from Docker hub. No container with unraid template available. Add container button Name: ClamAV Repository: mk0x/docker-clamav:alpine Icon URL: http://www.clamav.net/assets/clamav-trademark.png Extra Parameters: -p 3310:3310 --hostname=clamavsrv --restart=unless-stopped Network Type: "Custom : Br0" (change to fit your network and environment) Fixed IP address (optional): 192.168.1.24 (change to fit your network and environment) Added extra path for logs, want easy access: Container Path: /var/log/clamav. Host path: /mnt/user/appdata/clamav/logs/ See screenshots in earlier post. Edit 2: Added my template. Edit 3: Switched to the smaller alpine based image. my-ClamAV.xml

The container solution runs much faster compared to having it in the same container as the Nextcloud one. For some reason. When the solution is up, you can use files from here to test your install: https://www.eicar.org/?page_id=3950

Yeah. I have talked about that plug-in all the time. I also added clamav with apk and got it working but adding clamd and other stuff will need some more configuring, so I went the other route as in my post. Seem to be working fine and the container handles auto update and so on.

Really? Hm. Where? Can't find it. I can find the plugin used to talk to ClamAV. https://apps.nextcloud.com/?search=antivirus

I looked for clamav in the container first. The plugin needs clamscan /usr/bin/clamscan bash: /usr/bin/clamscan: No such file or directory Edit: One solution: Added this container: https://hub.docker.com/r/mkodockx/docker-clamav/ Configured the plugin in Nextcloud to connect to ClamAV-container using ip and port 3310.

Could ClamAV be added to this container? This plugin looks good and make use of it: https://apps.nextcloud.com/apps/files_antivirus If I could add it myself (and keep it after updates), please tell me how.

Click the logo?