@reboot

[hongkongkiwi]

Does ofelia support @reboot command?

[BartoszBartniczak]

I don't think so 😞 Have you found any solution for this?

[hongkongkiwi]

No solution for this.

I currently use supercronic to run jobs inside my docker. It's very lightweight and simple, but alas, that too does not support @reboot command.

To get around this, I actually run a shell script, which first runs the command, then runs supercronic. Messy but workable.

[BartoszBartniczak]

Supercronic looks good, but I need to have a separate container with cron jobs. I see, that supercronic does not support that feature.

So far, I added entrypoint.sh file with startup jobs, to one of my containers. It replaces @reboot pretty good.

[hongkongkiwi]

I don't understand what you mean. I use supercronic to run other docker containers.

• Master Cron Container (sueprcronic) based on library/docker - with mounted crontab & docker sock file from host
• Sub docker containers are started by my cron job (just a normal docker run command)

@reboot is better because it handles failures in a more streamlined way, using the entrypoint is less ideal because you need to somehow handle failure, plus the logging is a different format. Other than that it is acceptable.

[BartoszBartniczak]

OK, maybe I did a mistake. I did not know that I can use docker.sock to run command on the other container. Do you have any example of using this? I think I understand this, but working example would be great.

Yeah, I know that running cron jobs in entrypoint is not the best idea, but lucky me, all my cron jobs are logged in database either. So far, I can use it this way.

[taraspos]

@hongkongkiwi, I'm not sure that I understand the question.
What is

@reboot command

exactly? Like to actually reboot docker host? 🤔

[hongkongkiwi]

No, @reboot runs when the crond service is started upon boot.

If you take the following, it would look like this:
@reboot do-something-cool
@hourly do-something-cool

So, the reboot command is immediately run when the daemon is started, the reason it's called reboot is in a normal linux system, this happens once upon boot, in our docker obviously it would be each time the docker is restarted. These are conventions for modern cron daemons, the @hourly is just a nice helper since it can be also done with something like * 0 * * , but reboot is a special flag.

Take syncing files, you will want it to happen immediately to get things up to date, then you will want it at a regular interval after that.

[taraspos]

Got it, thanks!

[taraspos]

related #79

[jtbry]

For anyone still reading this, this issue is solved in PR #184. You can use the fork for now if you need the functionality.