unable to define clamav-host correctly #41

New Issue

michael · 2026-01-19T18:28:43Z

michael commented

2026-01-19 18:28:43 +00:00

Originally created by @zenjabba on GitHub.

In my docker-compose I'm using the following line

command: "--listener :8080 --provider local --basedir /basedir --purge-days 10 --purge-interval 2 --max-upload-size 10000000 --clamav-host nextav --perform-clamav-prescan true"

but when I upload a file I'm getting

2023-12-20T19:51:00.535764246Z [transfer.sh]2023/12/20 19:51:00 dial unix nextav: connect: no such file or directory

I have clamav within the docker-compose

av:
image: mkodockx/docker-clamav:alpine
container_name: nextav
hostname: nextav
restart: unless-stopped
volumes:
- /opt/docker/clamav:/var/lib/clamav
- /var/run/clamav/:/var/run/clamav/

but not sure how to actually link up transfer with clamav as the hostname issue seems to causing me lots of problems.

Thanks

Originally created by @zenjabba on GitHub. In my docker-compose I'm using the following line command: "--listener :8080 --provider local --basedir /basedir --purge-days 10 --purge-interval 2 --max-upload-size 10000000 --clamav-host nextav --perform-clamav-prescan true" but when I upload a file I'm getting 2023-12-20T19:51:00.535764246Z [transfer.sh]2023/12/20 19:51:00 dial unix nextav: connect: no such file or directory I have clamav within the docker-compose av: image: mkodockx/docker-clamav:alpine container_name: nextav hostname: nextav restart: unless-stopped volumes: - /opt/docker/clamav:/var/lib/clamav - /var/run/clamav/:/var/run/clamav/ but not sure how to actually link up transfer with clamav as the hostname issue seems to causing me lots of problems. Thanks

michael commented

2026-01-19 18:28:43 +00:00

@paolafrancesca commented on GitHub:

hi @zenjabba support for clamav scan over the network was removed with https://github.com/dutchcoders/transfer.sh/pull/389, introducing the possibility to enbale clamav scan on upload

I apologise, the --clamav-host flag has not being renamed to --clamav-path, but it only supports a path now

Please let me know if you need any help in sharing the path between containers in your docker-compose file

@paolafrancesca commented on GitHub: hi @zenjabba support for clamav scan over the network was removed with https://github.com/dutchcoders/transfer.sh/pull/389, introducing the possibility to enbale clamav scan on upload I apologise, the `--clamav-host` flag has not being renamed to `--clamav-path`, but it only supports a path now Please let me know if you need any help in sharing the path between containers in your docker-compose file

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dutchcoders/transfer.sh#41