benzino77

Yes, the changed command in CRA deployment should force CRA to wait for Clamavd to be accessible. Here is the full description of `wait-for-it` command: [link](https://github.com/vishnubob/wait-for-it)

You are right. You should talk with someone from your DevOps team to help you troubleshoot this problem. On my side I can tell that I have performed some tests....

Check your logs why clamavd stops working after a day. There is a comment above pointing that assigning more memory to clamavd deployment solves the problem.

Well, to tell the truth I can't remember what was the reason .... ;) Make a PR with that change so we can work on it together. Using reverse proxy...

Hi! Do you have CRA and ClamAV started in docker?

But CRA is started inside container? If so, you cannot use localhost/127.0.0.1 as Clamavd address because localhost/127.0.0.1 inside container is not the same as your host ;)

OK. So here is the problem: you have not specified `CLAMD_IP` env variable for CRA container so it defaults to localhost/127.0.0.1 (you just copy paste command from README without pointing...

You should not use it that way - that address will change every time you restart clamavd container. Have a look in the examples [folder](https://github.com/benzino77/clamav-rest-api/blob/master/examples/docker-compose.yml) If you do not want...

CRA will not start if there is no clamav daemon available (or I should rather say there is no clamavd with open 3310 port available). As I can see from...

> Thank you, that worked! I think it is better to update the `README` about the same, since I do not see this info there. Cheers! PRs are welcome ;)