TQ

Sure. I think that would be not too difficult. Feel free to open a PR if you have the time!

I'd recommend removing it with the below command. You can then use your "my-templates" to restore the old application and it's config. My bet is that it collides with another port, and in that case, you can simply change it. docker rm PufferPanel -f

https://docs.pufferpanel.com/en/latest/release-notes/2.6.0.html#steamgamedl

Application: https://pypi.org/project/matchering/

Application: https://tiddlywiki.com

Overview: PufferPanel is an open source game server management panel designed to be easy to use and easy to install. PufferPanel supports Minecraft, Forge, Spigot, Sponge, Source Dedicated Servers, BungeeCord, PocketMine, Forge, and much more. Application: https://www.pufferpanel.com Docs: https://docs.pufferpanel.com/en/latest/index.html First Run: Create a user: docker exec -it PufferPanel /pufferpanel/pufferpanel user add

Baserow is an open source no-code database and Airtable alternative. Create your own database without technical experience. Our user friendly no-code tool gives you the powers of a developer without leaving your browser. Application: https://baserow.io/

Overview: Support for flatnotes - A self-hosted, database-less note taking web app that utilises a flat folder of markdown files for storage. Application: https://github.com/Dullage/flatnotes

Latest branch updated. Please re-pull and LMK.

I will check on it tonight. Not sure how the arch changed.

It should be quite possible, yes. I do not use Nextcloud so bit of a challenge for me.

I agree, it feels dirty to chmod 777 to a dir. You can do the below to the directory to resolve the issue. chmod -R u-x,go-rwx,go+u,ugo+X /mnt/cache/appdata/clamav chown -R nobody:users /mnt/cache/appdata/clamav Note: hack that I use, when creating directories and such via ssh, I use the following sudo -u nobody -g users 'command here' ...so that the perms dont come back to bite me.

That is the output of the command to run the container. You can see the logs by either clicking the icon in the Docker tab, and choosing "Logs" or by running the command below from an SSH session. docker logs -f ClamAV

That is strange. I just rebuilt the container on my test Unraid server to ensure it was pulling new and starting with new config. I passed the -i and -f parameters respectively, and all passed and worked. I do see two potential issues with your configuration. Wondering if you're adding the parameters to the "Extra Parameters" instead of "Post-Arguments" options. I added the following parameters to that section and it runs normally. -i --log=/var/lib/clamav/log.log --max-filesize=4096M --file-list=/scan/file-list.txt Also, parameters should be from the "container's" perspective. I pass the file list using the container's path. Output: 2023-01-28T16:05:17+00:00 ClamAV process starting Updating ClamAV scan DB ClamAV update process started at Sat Jan 28 16:05:17 2023 daily.cvd database is up-to-date (version: 26795, sigs: 2018570, f-level: 90, builder: raynman) main.cvd database is up-to-date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr) bytecode.cvd database is up-to-date (version: 333, sigs: 92, f-level: 63, builder: awillia2) Freshclam updated the DB ClamAV 0.104.3/26795/Sat Jan 28 08:27:17 2023 Scanning /scan WARNING: Only scanning files from --file-list (files passed at cmdline are ignored) ----------- SCAN SUMMARY ----------- Known viruses: 8650505 Engine version: 0.104.3 Scanned directories: 4 Scanned files: 6 Infected files: 0 Data scanned: 0.15 MB Data read: 5678.47 MB (ratio 0.00:1) Time: 26.245 sec (0 m 26 s) Start Date: 2023:01:28 16:05:17 End Date: 2023:01:28 16:05:43 2023-01-28T16:05:43+00:00 ClamAV scanning finished

Hmm. Well, definitely should add timestamp to `stdout` next update. (adds to my to-do list) So, are you referring to the pop-up in the Unraid GUI that shows the previous virus found message? Just want to make sure I understand fully.

In the logs they should be time stamped. Is it finding the file again after deletion, or is it showing the previous infected file with previous time stamped entry? Can you post a section of the logs for view?

That's really for you to decide. ClamAV has never had a webUI afaik. Take a look at all my documentation (from the first post) and you'll find the answers to your questions.

Unfortunately, I'm not sure. I know this one works using the template in CA.

It would appear that this is not my container. I'm not notifying `clamd` due to it not being present in my build.

I cannot reproduce. Here is my start up just moments ago... 2022-11-05T17:43:48+00:00 ClamAV process starting Updating ClamAV scan DB ClamAV update process started at Sat Nov 5 17:43:49 2022 daily database available for update (local version: 26706, remote version: 26711) Testing database: '/var/lib/clamav/tmp.e364402c7f/clamav-ee0a95b108d7db8f9cd5ab0ba1ab6c53.tmp-daily.cld' ... Database test passed. daily.cld updated (version: 26711, sigs: 2010014, f-level: 90, builder: raynman) main.cvd database is up-to-date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr) bytecode.cvd database is up-to-date (version: 333, sigs: 92, f-level: 63, builder: awillia2) WARNING: Clamd was NOT notified: Can't connect to clamd through /run/clamav/clamd.sock: No such file or directory Freshclam updated the DB ClamAV 0.104.3/26711/Sat Nov 5 07:49:31 2022 This almost seems as if there is a permission issue updating the c?d files. Try this: If that does not solve it, delete all contents of your ClamAV appdata folder and restart the container. /cc @SwampyShadow

I just updated my container on my backup Unraid and ran it. Ran over 2 hours. Output. Freshclam updated the DB ClamAV 0.104.3/26603/Sat Jul 16 07:57:28 2022 Scanning /scan ----------- SCAN SUMMARY ----------- Known viruses: 8622360 Engine version: 0.104.3 Scanned directories: 674 Scanned files: 19907 Infected files: 0 Data scanned: 118466.76 MB Data read: 266611.65 MB (ratio 0.44:1) Time: 7262.284 sec (121 m 2 s) Start Date: 2022:07:16 15:03:23 End Date: 2022:07:16 17:04:25 2022-07-16T17:04:25+00:00 ClamAV scanning finished I think something is up with your permissions on those files.

Have you tried changing this? --bytecode-timeout=N - set bytecode timeout (in milliseconds)

Squid is, of course, correct. You can check the documentation that I have provided on Docker Hub and pass those parameters via Post Arguments in the container config.

From what I've experienced, it's usually due to permissions on the appdata folder for Clam. Try to run that aforementioned fix for perms and see if that helps.

chmod -R u-x,go-rwx,go+u,ugo+X /mnt/cache/appdata/clamav chown -R nobody:users /mnt/cache/appdata/clamav