Restarted build.

OK, this did not work. Apparently the environment variable is cleared before the cron job runs. Does this actually work when setting VIRUSMAILS_DELETE_DELAY?

There are a few options left, but they all have to be done in the start script:

1. Setting VIRUSMAILS_DELETE_DELAY in the crontab
2. Changing virus-wiper to take a parameter and setting up the cron job in the start script with the value as a parameter.
3. Creating virus-wiper with the actual value already in place
4. Writing environment variables to a file and reading it in virus-wiper

I would vote for (2) as I think this is the most straight-forward solution.

Hmm it seems that current implementation does not work as expected, you're right (i've done that myself).
When I execute virus-wiper, manually it works.
It does not when triggered by CRON.

I think that putting the ENV in /etc/environment should do the trick if you want to try.

The start script will now write the variable to /etc/environment. I tested it manually this time (by adding a cron job which runs every minute)

Oh, and there is a small fix by setting ONE_DIR to 0 in the Dockerfile.

Thanks @danielpanteleit