Skip to content
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 jobs return "System error" #144

Closed
karel-3d opened this Issue Sep 25, 2014 · 7 comments

Comments

Projects
None yet
6 participants
@karel-3d
Copy link

commented Sep 25, 2014

I am trying to run cronjobs on my docker image; they never run, and all that happens is that "System error" is written on the output.

It doesn't matter what the cronjob is, how often it is, and so on. There is zero other log output.

The same thing happened when I tried to run a "vanilla" ubuntu image and "cron -f", so I can't really tell where is the actual error.

The same thing happened with 0.9.13 (where the "System error" is written on STDOUT) and with 0.9.10 (where the "System error" is written in /var/log).

The "outside" system is Trusty on Linode. I have zero clue where is the error.

@karel-3d

This comment has been minimized.

Copy link
Author

commented Sep 25, 2014

(It seems I will end up replacing cron jobs with my own bash script that does essentially the same as cron until this is solved.)

@FooBarWidget FooBarWidget added this to the 0.9.16 milestone Jan 19, 2015

@FooBarWidget FooBarWidget added the bug label Jan 19, 2015

@FooBarWidget

This comment has been minimized.

Copy link
Member

commented Jan 19, 2015

Marking this for 0.9.16. Sorry for the delay.

@FooBarWidget

This comment has been minimized.

Copy link
Member

commented Jan 19, 2015

I think this is a duplicate of #115. I'll fix both at the same time.

@Erfa

This comment has been minimized.

Copy link

commented May 6, 2015

I had the exact same problem, just a "System error" in STDOUT from cron. In my case, the problem was that I used the --net="host" parameter when running the application. When I removed that, it worked fine.

@vimondketil

This comment has been minimized.

Copy link

commented May 20, 2015

I can confirm the same behaviour as @Erfa – i get a "CRON[531]: System error" when running in --net="host" mode. Is this to be expected, or is it fixable?

@banjoey

This comment has been minimized.

Copy link

commented Nov 2, 2015

+1 for --net="host" exposing the problem. Apparently affects debian base images as well: docker-library/official-images#744

Has anyone found a workaround?

@ezrast

This comment has been minimized.

Copy link

commented Nov 5, 2015

@banjoey There's some discussion of this issue at moby/moby#5899 - the suggested workaround is adding "--pid=host" to the run command, which works for me. Keep in mind that this will expose the host's process information to the container.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.