TQ

You can update if you wish. My builds are waiting for all dependencies to be updated before I build for Clam. I check the Alpine site weekly to know when I can update stable and edge branches.

Occasionally I run into this, and the fix is to chmod and chown the files/folders.

I didnt have this issue before, but after recreating the file structure, I am getting the same error. If you run the built-in script `newperms /path/to/your/db/folder` it will resolve. That script effectively does the following... chmod -R u-x,go-rwx,go+u,ugo+X '/path/to/your/db/folder' chown -R nobody:users '/path/to/your/db/folder'

I literally searched the documentation page on the previous comment for fml https://github.com/itzg/docker-minecraft-server/blob/master/README.md#jvm-options

Just follow the same logic you would when running one normally. Put the mods/resources in the appropriate folder you mapped. i.e. `/mnt/user/appdata/minecraft/` Full Documentation for this container - https://github.com/itzg/docker-minecraft-server/blob/master/README.md

Something must be wrong with the package on Spigot resources. I did the same and got the same result. Chose a different resource and no issue downloading and moving it into the plugins directory.

Merged the PR. Thanks @Squid

It's fixed via the PR from @Squid. I understand the frustration that this could cause and apologize for the oversight. However, I would caution anyone using CA or non-CA containers to review the settings the template offers prior to running it. This will save much heartache.

Sounds about right.

I've used @ich777 plugins/containers and all of them are great. For some reason I could not get the prometheus AdGuard exporter to work. So I built this template to use based on the same upstream repo. Repo: ebrianne/adguard-exporter: Adguard exporter based on eko/pihole-exporter (github.com)

No vulns detected. Updated the images to address the vulns found post-scan.

Precisely. Squid posted a script that I linked in the original post.

Wherever you're mounting those directories, you do not have access. If you've not mounted those directories, then your docker.img file is full.

Certainly will give it a whirl.

Pleased to release this amazing dockerized version of Minecraft from itzg. Full Documentation for this container can be found here. Application: Minecraft https://minecraft.net https://docker-minecraft-server.readthedocs.io/en/latest/configuration/server-properties/

You've been rate limited. Are you behind a large NAT? That error indicates rate limited. If you continue to have issues, rebuild the container and try again. If that doesn't work, try manually installing the main db files into a bind mounted dir and see if that works.

Hi Binhex. Recently, the sabnzbd container started griping about unrar version 0.00. I noticed that the options to unpack + delete no longer work and downloads are not be extracted. I've validated that the container has `par2cmdline` as well as `unrar`. Do you know what this issue is? I can run unrar from inside the container no issue, but sab seems to think I have version 0.00 and it wont extract.

Thanks @vroommm

Update. I have updated to 0.103.2-r0 and merged a couple of PRs. For my scan today, the `LibClamAV` issue seems resolved.

Edit the container settings and remove the below:

Have you tried removing the -i post-arg ?

I don't think so. I stuff my docker.img file elsewhere and I was seeing the issue prior to the latest build. I'll run another scan and see if I indeed still see the behavior. ...working on a clamd version as well.

It gets passed to the clamscan binary as an arg. REF: clamscan(1): scan files/directories for viruses - Linux man page (die.net) -i, --infected Only print infected files.

Sorry guys, life's priorities always win. Just updated the "Latest" tagged image (which the Unraid version is working from) Alpine: 3.13 ClamAV: 0.103.1-r0 I just scanned a decent chunk of files and did not see the behavior we all were seeing. 2021-03-01T03:45:47+0000 ClamAV process starting Updating ClamAV scan DB ClamAV update process started at Mon Mar 1 03:45:47 2021 daily database available for download (remote version: 26094) Testing database: '/var/lib/clamav/tmp.e75353b543/clamav-ded1d73233782def9a1cb364ec3fb77b.tmp-daily.cvd' ... Database test passed. daily.cvd updated (version: 26094, sigs: 3955353, f-level: 63, builder: raynman) main database available for download (remote version: 59) Testing database: '/var/lib/clamav/tmp.e75353b543/clamav-462eb68c40e1e0c4badfd63fb77fc22d.tmp-main.cvd' ... Database test passed. main.cvd updated (version: 59, sigs: 4564902, f-level: 60, builder: sigmgr) bytecode database available for download (remote version: 332) Testing database: '/var/lib/clamav/tmp.e75353b543/clamav-27c26d1f3ba016bc7ba80a8909c019f2.tmp-bytecode.cvd' ... Database test passed. bytecode.cvd updated (version: 332, sigs: 93, 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.103.1/26094/Sun Feb 28 12:14:26 2021 Scanning /scan ----------- SCAN SUMMARY ----------- Known viruses: 8505015 Engine version: 0.103.1 Scanned directories: 2867 Scanned files: 35955 Infected files: 0 Data scanned: 44733.52 MB Data read: 34502.84 MB (ratio 1.30:1) Time: 6768.326 sec (112 m 48 s) Start Date: 2021:03:01 03:46:10 End Date: 2021:03:01 05:38:58 2021-03-01T05:38:58+0000 ClamAV scanning finished Pull the latest and cross your fingers.

Great idea. I think for this to be something that actually works, this container would not be the one. I'd (or someone else) would have to write one for clamd (the daemon used for ClamAV), as this one only updates the dbs and runs a scan.