New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cron service does not work with overlay storage driver: tail: unrecognized file system type 0x794c7630 for '/var/log/cron.log' #2

Closed
fkoester opened this Issue Jul 26, 2016 · 5 comments

Comments

Projects
None yet
3 participants
@fkoester
Contributor

fkoester commented Jul 26, 2016

When using docker together with the overlay storage driver, the cron service of letsencrypt-manager fails to start. Log says:

Attaching to dockerletsencryptmanager_cron_1
cron_1  | tail: unrecognized file system type 0x794c7630 for '/var/log/cron.log'. please report this to bug-coreutils@gnu.org. reverting to polling
ERROR: Aborting.
@fkoester

This comment has been minimized.

Show comment
Hide comment
@fkoester

fkoester Jul 26, 2016

Contributor

Fixed, please update.

Contributor

fkoester commented Jul 26, 2016

Fixed, please update.

@fkoester fkoester closed this Jul 26, 2016

@fabiomaia

This comment has been minimized.

Show comment
Hide comment
@fabiomaia

fabiomaia Apr 20, 2017

Thanks! Your fix was helpful in my own problem.

fabiomaia commented Apr 20, 2017

Thanks! Your fix was helpful in my own problem.

@fkoester

This comment has been minimized.

Show comment
Hide comment
@fkoester

fkoester Apr 21, 2017

Contributor

@faviouz Glad I could help! For later reference: The root cause of this problem is that the version of tail (package coreutils) in the Debian base image is too old and does not know the overlay filesystem. Using a docker volume for /var/log works around this by using the host's filesystem (ext4 in my case) and tail does not need to know overlay.

Contributor

fkoester commented Apr 21, 2017

@faviouz Glad I could help! For later reference: The root cause of this problem is that the version of tail (package coreutils) in the Debian base image is too old and does not know the overlay filesystem. Using a docker volume for /var/log works around this by using the host's filesystem (ext4 in my case) and tail does not need to know overlay.

@tiny1990

This comment has been minimized.

Show comment
Hide comment
@tiny1990

tiny1990 Sep 8, 2017

can you tell me how to fix this? which PR

tiny1990 commented Sep 8, 2017

can you tell me how to fix this? which PR

@fkoester

This comment has been minimized.

Show comment
Hide comment
@fkoester
Contributor

fkoester commented Sep 11, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment