You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am facing difficulties when using at to schedule a one-time job after a certain time like this:
at -f ./my-script.sh now + 1 minute
Using atq I can verify that the job is actually scheduled. But the job won't start before scheduling another job execution using at. I am wondering if running this inside a container might be the cause. What are your thoughts on this?
If this is actually caused by the execution inside the container, than having supercronic support this case might be valuable.
The text was updated successfully, but these errors were encountered:
a) I am currently facing the following problem: I need to start a job inside my container with a certain time offset (+1 min) after container start. Normally I would use at for this. Unfortunately I am facing issues when using "at" inside a container (works perfectly outside a container). My first thought was that this might by caused by the same things that hinder use of cron jobs inside a container and that led to the development of supercronic. Hence I was wondering what your thoughts on this are.
b) One solution to the problem would be to extend supercronic to support one-time asynchronous tasks. As this is not super clean I would fully understand if you had any objections.
I am facing difficulties when using at to schedule a one-time job after a certain time like this:
Using
atq
I can verify that the job is actually scheduled. But the job won't start before scheduling another job execution using at. I am wondering if running this inside a container might be the cause. What are your thoughts on this?If this is actually caused by the execution inside the container, than having supercronic support this case might be valuable.
The text was updated successfully, but these errors were encountered: