TQ

Updated.

Edit the existing baserow container and then scroll to the bottom. You'll see a button that says save. When you click save it will output the docker run command. You can then take the arguments relevant to the pg-upgrade container and paste those in. Hopefully this solves the issue for you and @da.ju

You're not using my container.

I made a spot in the template for these:

You can add your --exclude to the post-args section. Per the man page, you must use REGEX for the exclude option. I tested this in my environment. --exclude="^(.*\.iso)$"

No, it is a file that has the contents that is listed below. Yes. -f is the shorthand version of --file-list

I was able to utilize the --file-list option and scanned a specific directory (a subdirectory of /scan) ... daily.cld database is up-to-date (version: 27178, sigs: 2052470, 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: 334, sigs: 91, f-level: 90, builder: anvilleg) Freshclam updated the DB ClamAV 1.2.1/27178/Wed Feb 7 03:35:39 2024 Scanning /scan WARNING: Only scanning files from --file-list (files passed at cmdline are ignored) ----------- SCAN SUMMARY ----------- Known viruses: 8684340 Engine version: 1.2.1 Scanned directories: 29 Scanned files: 1427 Infected files: 0 Data scanned: 65.70 MB Data read: 25121.64 MB (ratio 0.00:1) Time: 271.660 sec (4 m 31 s) Start Date: 2024:02:07 16:40:51 End Date: 2024:02:07 16:45:23 2024-02-07T16:45:23-06:00 ClamAV scanning finished Latest reconfigured container options: docker run -d --name='ClamAV' --net='bridge' --cpuset-cpus='0,1' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="" -e HOST_CONTAINERNAME="ClamAV" -e 'USER_ID'='99' -e 'GROUP_ID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://github.com/tquizzle/clamav-alpine/blob/master/img/clamav.png?raw=1' -v '/mnt/cache/appdata/downloads/':'/scan':'ro' -v '/mnt/cache/appdata/clamav':'/var/lib/clamav':'rw' 'tquinnelly/clamav-alpine' -i --file-list=/var/lib/clamav/scanfiles --log=/var/lib/clamav/log.log --max-filesize=2040M File list: scanfiles /scan/subdirectory/another-directory The key point here is that the reference to these supporting files passed in as vars are from the containers path, not the host. Hope this helps anyone facing this challenge.

Permissions have nothing to do with @Masterwishx script. The should inherit from the UID/GID passed via the container.

Maybe try without scan targets txt file. In the errors, you can see the container cannot open that file

Permissions are correct. But the error persists. Perhaps your volume mounts are not correct. Do you have a volume mounted for the directory you are trying to scan as well as the file that has the scan folders in it? From my Github documentation: docker run -d --name=ClamAV \ --cpuset-cpus='0,1' \ -v /path/to/scan:/scan:ro \ -v /path/to/sig:/var/lib/clamav:rw \ tquinnelly/clamav-alpine -i --log=/var/lib/clamav/log.log --max-filesize=2048M That path to "signatures" is the path you are working with. Is that path mounted? If not, you have to mount it before calling a file in it. It also is relevant to the container path, not the host. --file-list: Can't open file /scan/appdata/clamav/clamavtargets.txt If you've mounted it as in my example, it would be: --file-list=/var/lib/clamav/clamavtargets.txt

Read at minimum

ERROR: --file-list: Can't open file /scan/appdata/clamav/clamavtargets.txt WARNING: Only scanning files from --file-list (files passed at cmdline are ignored) ERROR: --file-list: Can't open file /scan/appdata/clamav/clamavtargets.txt WARNING: Only scanning files from --file-list (files passed at cmdline are ignored) ERROR: --file-list: Can't open file /scan/appdata/clamav/clamavtargets.txt This error is at the top. This is your issue. You've explicitly set "--file-list" but the container cannot see that file, or has no permission to it.

I would start with the docker logs of the container. See what the errors tell you.

Thanks Masterwishx for highlighting this. Indeed, 99:100 is the "Docker Safe Permission" user:group that is set when you run that script (nobody:users). Also, the built-in "newperms" runs this same change. If you have permission issues in your environment, I'd recommend either of these options on your ClamAV folder and running again.

Good catch! XML is updated.