On Sun, 10 Oct 2021, Taylor Schley via clamav-users wrote:
ClamD setup in the docker container is:
`/run/clamav/clamd.socket`
Which is bound to `/tmp/clamd.socket` on the host MacOS.
The following works from inside of the container:
`clamdtop ‘/run/clamav/clamd.socket’`
The fo
Hi there,
On Sun, 10 Oct 2021, Taylor Schley via clamav-users wrote:
On Oct 10, 2021, at 11:35 AM, G.W. Haywood via clamav-users
wrote:
On Sun, 10 Oct 2021, Taylor Schley via clamav-users wrote:
On Fri, 8 Oct 2021, Taylor Schley via clamav-users wrote:
I have setup clamav using the docker c
Here is the response:
2021/10/10 12:14:57 socat[38274] E connect(5, LEN=19 AF=1 "/tmp/clamd.socket",
19): Connection refused
> On Oct 10, 2021, at 11:35 AM, G.W. Haywood via clamav-users
> wrote:
>
> Hi there,
>
> On Sun, 10 Oct 2021, Taylor Schley via clamav-users wrote:
>>> On Fri, 8 Oct
Hi there,
On Sun, 10 Oct 2021, Taylor Schley via clamav-users wrote:
On Fri, 8 Oct 2021, Taylor Schley via clamav-users wrote:
I have setup clamav using the docker container available on Docker
Hub. Clamd is running with in the container and the socket path is
mounted, however when I attempt t
ClamD setup in the docker container is:
`/run/clamav/clamd.socket`
Which is bound to `/tmp/clamd.socket` on the host MacOS.
The following works from inside of the container:
`clamdtop ‘/run/clamav/clamd.socket’`
The following does not work on the host MacOS.
`clamdtop ‘/
Hi there,
In INSTALL.md for 0.104.0 it says
[quote]
1. **Single-config generators** (Unix Makefiles, Ninja)
These generate a build system that can only build a single build type.
With a single-config generator, you need to specify the build type up
front. You can do this using the `-C`
