short answer
add this line to your dockerfile
RUN sed -i '/session required pam_loginuid.so/c#session required pam_loginuid.so' /etc/pam.d/crond
the long answer
from what I understand issue is related to differences in the kernal between CoreOS & Unbutu. this in-turn causes a pam security issue.
to figure it our first needed to turn on logging for cron (since we are in docker normal startup is not executed). run
service rsyslog start
service crond restart
the cron log had this error (located here /var/log/cron)
FAILED to open PAM security session (Cannot make/remove an entry for the specified session)
so then I took a look at the security log, and it had this error (located here /var/log/secure)
pam_loginuid(crond:session): set_loginuid failed
some more googling and found I needed to modify my pam cond config (found here /etc/pam.d/crond)
edit this file and comment out the following line
#session required pam_loginuid.so
restart crond and all should be good
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…