-
Notifications
You must be signed in to change notification settings - Fork 482
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
dockerized crontab-ui jobs will not run without trick #208
Comments
Hey @tayyebi I don't completely understand your problem, but why wouldn't you add your username as a part of the "Command" field? |
Unrelated to your issue, but you probably understand this better than I do:
|
Dear @icemtel it's working like a charm!
Because if add add the username in |
Short answer: YES. As I wanted to use this container to configure cronjobs on my host machine, I linked If I want to summarize, it will be so nice, if we could have another field, right after cron expression (and before Cheers. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
hey @tayyebi i have the same problem.. i got
in /var/log/syslog |
nevermind..
agree, i hope it is on the roadmap.. thanks.. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Before all thank you for your amazing project!
I'm using this cool tool on docker. My
docker-compose.yml
is shown below:As you already know **If we are decided to add a cronjob to cron.d, we have to mention the username, after time configuration.
So, this will work for
crontab -e
:But it will definitely not work in
cron.d
and it should be:As you can see in the image below, I used the last time text box to define my username! Can we add an input for that?
(I'll be honored to volunteer this task, if you let me know your idea about it.)
Cheers
The text was updated successfully, but these errors were encountered: