Container Won't Start Up about docker-clamav HOT 12 CLOSED

You need to wait a moment, clamd needs to start first - freshclam will try again after some time

from docker-clamav.

Hello @khollycap ,
thank you very much for posting your issue. I can reproduce the error.

It looks like an interruption of the connection during the database download.

from docker-clamav.

As I read the infos of clamav Discord, there is a various blocking of clients established via Cloudflare.

So the old versions are blocked, there is rate limiting per client and per IP as well. I'm not sure somewhat more is blocked

from docker-clamav.

Did you try the alpine-edge version? It has the latest available clamav version integrated. For me that one works.

from docker-clamav.

The alpine image uses clamav in version 0.103.3-r0.
The alpine edge image uses clamav in version 0.104.2-r0

from docker-clamav.

That one gets stuck on the daily database download for me.

from docker-clamav.

Well I was able to reproduce the error again, it seems to me it has something to do with docker desktop.

If I run it with docker from terminal, there is no error. Could you try following in your terminal:

docker run -d mkodockx/docker-clamav:alpine

from docker-clamav.

Started from docker desktop:

Started from terminal exact same image:

from docker-clamav.

I got this ^ error after running that command

from docker-clamav.

I'm not sure but it might be because of the different std attachment and tty configuration:

From CLI:

[
    {
        "AppArmorProfile": "",
        "Args": [
        ],
        "Config": {
            "AttachStderr": false,
            "AttachStdin": false,
            "AttachStdout": false,
            "Cmd": [
                "/bootstrap.sh"
            ],
            "Domainname": "",
            "Entrypoint": null,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
            ],
            "ExposedPorts": {
                "3310/tcp": {
                }
            },
            "Hostname": "e8da6560714a",
            "Image": "mkodockx/docker-clamav:alpine",
            "Labels": {
                "maintainer": "Markus Kosmal <[email protected]>"
            },
            "OnBuild": null,
            "OpenStdin": false,
            "StdinOnce": false,
            "Tty": false,
            "User": "clamav",
            "Volumes": null,
            "WorkingDir": ""
        },
        [...]
        
    }
]

From Docker Desktop:

[
    {
        "AppArmorProfile": "",
        "Args": [
        ],
        "Config": {
            "AttachStderr": true,
            "AttachStdin": false,
            "AttachStdout": true,
            "Cmd": [
                "/bootstrap.sh"
            ],
            "Domainname": "",
            "Entrypoint": null,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
            ],
            "ExposedPorts": {
                "3310/tcp": {
                }
            },
            "Hostname": "ac6770f990ac",
            "Image": "mkodockx/docker-clamav:alpine",
            "Labels": {
                "maintainer": "Markus Kosmal <[email protected]>"
            },
            "OnBuild": null,
            "OpenStdin": false,
            "StdinOnce": false,
            "Tty": true,
            "User": "clamav",
            "Volumes": null,
            "WorkingDir": ""
        },
        [...]
    }
]

from docker-clamav.

I am running into same issue on linux x64 docker. I thought it's getting the connection refused because I run through vpn, but I tried the container outside vpn and same result.
image: mkodockx/docker-clamav:alpine-idb-amd64 - gets connection refused
image: mkodockx/docker-clamav:latest - gets connection refused
image: mkodockx/docker-clamav:alpine-edge - never initializes with ^Clamd was NOT notified: Can't connect to clamd through /run/clamav/clamd.sock: No such file or directory
image: mkodockx/docker-clamav:alpine - is the only tag that comes up for me atm

I only run this one instance of clam (I also run mailcow which uses clam, but I believe they have set up their own mirror) and I don't believe that would be putting undue pressure on their servers, more likely my public ip and vpn ip endpoints are getting banned on clam's side if they outright ban huge blocks of ip addresses. At the end of the day though, what do I know.

from docker-clamav.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from docker-clamav.