As I described in an issue a few weeks ago, I was seeing an error in my logs every time I started the letsencrypt container for my Docker Flow Proxy stack. I resolved it by creating /var/log/crond.log as an empty file early in the Dockerfile to ensure that it always exists at start-up.
I've had this running on my development server (in staging mode) for a few weeks now without issue.
n1b0r
commented
6 years ago
As I described in an issue a few weeks ago, I was seeing an error in my logs every time I started the
letsencryptcontainer for my Docker Flow Proxy stack. I resolved it by creating/var/log/crond.logas an empty file early in the Dockerfile to ensure that it always exists at start-up.I've had this running on my development server (in staging mode) for a few weeks now without issue.