[Question] ClamAV being used internally with NGINX about docker-clamav HOT 7 CLOSED

I am not the maintainer here ;) Just try to help out!
Wondering why this happens at all, afaik it should not. How have you definded nextcloud_clamav? Is it used by another service as well?
On the other hand I would just ditch the VOLUME declaration in the Dockerfile and add documentation for the sample compose which directory should be mapped. Once my current multi-arch PR is approved I could issue a new PR to remove the Dockerfile VOLUME.

from docker-clamav.

I would treat the docker-compose provided in here just a very basic example. Will try to work in the volume issue this week and update the sample compose and readme then.

• remove VOLUME from Dockerfiles
• update README with persistency instruction
• update sample compose to reflect volume usage

from docker-clamav.

I think it is valid to declare the VOLUME within the Dockerfile. You still can specify where to mount it (docker run -v /my/path/:/var/lib/clamav).
Can you post your compose file?

from docker-clamav.

I tried that and it just makes two volumes. Both the one you specified and the one I have listed in my compose file. The AV part of my compose file looks like this. Tell me if you need the entire file.

av:
  image: mkodockx/docker-clamav:alpine
  container_name: nextcloud-clamav
  networks: 
    - network1
  depends_on:
    - reverse_proxy
  volumes:
    - nextcloud_clamav:/var/lib/clamav
  environment:
    - NETWORK_ACCESS=internal
  restart: unless-stopped

from docker-clamav.

I have defined nextcloud_clamav like a volume. The volume declaration being removed from the docker file should fix this problem. This declaration should be in the docker compose file or in examples of terminal commands.

Summing it up, in addition to removing the volume declaration line in the docker file, the volume declaration line needs to be added to docker compose. Also, the example terminal lines needs to be updated to include the creation of the volume. I would also recommend adding:

restart: unless-stopped

For the purpose of this repository the changes would look like this.

av:
  debian: image: mkodockx/docker-clamav
  image: mkodockx/docker-clamav:alpine
  container_name: nextcloud-clamav
  networks: 
    - network1
  depends_on:
    - reverse_proxy
  volumes:
    - clamav:/var/lib/clamav
  restart: unless-stopped

The examples for terminal would be changed to:

docker run -d -p 3310:3310 -v clamav:/var/lib/clamav mkodockx/docker-clamav:alpine

docker run -v clamav:/var/lib/clamav mkodockx/docker-clamav:alpine-edge

from docker-clamav.

thanks to @WhiteBahamut closed by #72

from docker-clamav.

more PRs might come as I start to use the images more myself ;-)

from docker-clamav.