Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unable to define clamav-host correctly #595

Open
zenjabba opened this issue Dec 20, 2023 · 1 comment
Open

unable to define clamav-host correctly #595

zenjabba opened this issue Dec 20, 2023 · 1 comment

Comments

@zenjabba
Copy link

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

@aspacca
Copy link
Collaborator

aspacca commented Feb 22, 2024

hi @zenjabba support for clamav scan over the network was removed with #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 up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants