TQ
-
Posts
173 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by TQ
-
-
Full docs are here for use in docker.
-
I have set this up several times, but no amount of configurations on logging agents ever make their way to the OpenSearch stack.
Any tips?
-
On 5/3/2024 at 3:15 PM, Lugnut said:
How do I set a minimum value in the docker settings? When I first set the container up I set the value to 8G, I want it to fluctuate and not be constantly at that value.
Simply change the MEMORY environment value to the value you want.
-
Unsure how to trigger CA to update the image file, but the xml repo is updated.
-
21 hours ago, absoluttalent said:
Can we please get a fix for the docker Icon?
"Could not download icon https://maxcdn.icons8.com/Color/PNG/512/Gaming/minecraft_logo-512.png"
Updated.
-
On 4/18/2024 at 9:41 AM, ericreager said:
Hello - would anyone be able provide the steps for upgrading the data directory to be compatible with PostgreSQL 15, specific for this container on Unraid? I'm not exactly sure how to adapt the instructions from the Baserow site and I'm pretty paranoid about messing this DB up.
EDIT: I guess to clarify the part I'm shaky on, according to Baserow's instructions, I should stop the container, backup the instance, then run this in the Unraid console:
docker run \ --name baserow-pgautoupgrade \ # ALL THE ARGUMENTS YOU NORMALLY ADD TO YOUR BASEROW INSTANCE --restart no \ baserow/baserow-pgautoupgrade:1.24.2
I'm not sure exactly what I'm supposed to put in the # ALL THE ARGUMENTS YOU NORMALLY ADD TO YOUR BASEROW INSTANCE part.
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
-
On 3/5/2024 at 10:57 AM, ijuarez said:
this is what I get in the clamav docker logs
no sure how to fix that
You're not using my container.
-
3 hours ago, doogle said:
What do you mean by post args section?
I made a spot in the template for these:
-
11 hours ago, doogle said:
Anyone know how to get clamav to not scan .iso files. I would like to use it from the command line and not write a mile long script.
I have tried --exclude=*.iso and ?.iso but neither one worked.
If I have posted this in the wrong spot. please excuse me. I tried doing a search for this but when it returns 10 plus pages... what is the point of a search. This forum software kinda sucks.
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)$" -
2 hours ago, Revan335 said:
This is a directory?
No, it is a file that has the contents that is listed below.
2 hours ago, Revan335 said:This is the Entry of scanfiles but than he is a txt file and not a directory?
For example /scan/download/testfolder
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 finishedLatest 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=2040MFile list: scanfiles
/scan/subdirectory/another-directoryThe 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.
-
5 hours ago, Revan335 said:
OK, without that. Its Running longer.
This is the actually log:
2024-02-07T17:21:25+01:00 ClamAV process starting Unpdating ClamAV scan DB ClamAV update process started at Wed Feb 7 17:21:26 2024 daily database available for update (local version: 27177, remote version: 27178) Testing database: '/var/lib/clamav/tmp.ca29159519/clamav-29d3efd36d02b5b2da1c73d66e4f2cac.tmp-daily.cld' ... Database test passed. daily.cld updated (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) 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 1.2.1/27178/Wed Feb 7 10:35:39 2024 Scanning /scan
But why have my two Servers this Permission Error?
With or without the Improved Script from @Masterwishx
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 -
4 hours ago, Revan335 said:
Read is exist for everyone.
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=2048MThat 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.txtIf you've mounted it as in my example, it would be:
--file-list=/var/lib/clamav/clamavtargets.txt -
Whats Permissisons are needed?
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.txtThis 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.
-
A Scan Time from under 1 Minute is very strange.
That's to fast!
For multiple Folders or generally.
Who can I see the reason and fix that?
I would start with the docker logs of the container. See what the errors tell you. -
4 hours ago, Masterwishx said:
Do you have 99:100 permissions for Folder clamav As in container?
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.
-
1
-
-
1 hour ago, Helediron said:
I noticed a small issue with the Clamav container parameters. It uses path "/mnt/cache/appdata/clamav". I recently converted my cache to ZFS pool and named it "zfspool". So, i no longer have "cache" pool. A better value for the signatures folder would be "/mnt/user/appdata/clamav".
The "Fix Common Problems" plugin starts to yell about spurious "cache" folder under /mnt because of the parameter.Good catch!
XML is updated.
-
20 minutes ago, Revan335 said:
Do you mean this?
It's further up on the screen.
-
1
-
-
10 hours ago, Revan335 said:
Why we have two Entry's in the CA for ClamAV? But he reference the same Links.
One Official but this is not the Spotlight Entry.
What's the Difference/recommended?
Someone created the "Official", then pointed to my repo. SMH.
-
1
-
-
Reviewed the diags. Nothing stands out as being wrong.
I would do the following:
- Manually, review the docker containers you have as well as their "appdata" or "config" directories.
-
Review where that is on your cache drive (likely) and remove things from that directory that no longer align with containers your running.
- I have this issue after trying and testing tons of containers from the CA.
- `mc` can be your friend to quickly navigate **hint hint.
-
Run 'du' on your cache drive to see what folders are holding the massive amounts of data.
- /mnt/cache# du -h * --summarize
- Lastly, run newperms (which looks like you ran recently after looking at the logs) on your cache drive to reset permissions.
-
Welcome!
Sent from my iPhone using Tapatalk-
1
-
-
5 hours ago, robti said:
Any help for a newbie who ran this morning and get this, just installed and started with defaults ?
[Support] Minecraft-Server
in Docker Containers
Posted
Check the MEMORY section in the docs, here
https://github.com/itzg/docker-minecraft-server/raw/e6b525a65cc930264655894e9ff81562c63840c4/docs/configuration/jvm-options.md