cron starts even if ENABLE_CRON=FALSE

[deekue]

this line in 10-insync causes cron to start, even if ENABLE_CRON=FALSE

and then this line in services/04-cron/run adds another logrotate command to the root crontab.

is there any reason to add insync-headless to the crontab?
that instance won't be managed by s6

[tiredofit]

The entry in the cron startup is only for log rotation, which I don't believe I have any file logs built in on this image.

This sounds like a vendor issue with insync-headless - Some of this stuff is a real black box when getting it going under Docker so if it's doing that, does it add anything to the root crontab?