-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Schedule doesn`t start from command line #1812
Comments
I believe this will be fixed by https://dagster.phacility.com/D1226 |
one workaround you can use in the interim:
|
also @helloworld I think we're going to have to update the docs to describe how to get cron working in a container, the above Dockerfile won't launch cron. @newturok FYI you'll need something like the following in an #!/bin/sh
# see: https://unix.stackexchange.com/a/453053 - fix link-count
touch /etc/crontab /etc/cron.*/*
service cron start
export DAGSTER_HOME=/opt/dagster/dagster_home
for name in `/usr/local/bin/dagster schedule list --name --running`; do
echo $name;
/usr/local/bin/dagster schedule stop $name;
/usr/local/bin/dagster schedule start $name;
done
/usr/local/bin/dagit -h 0.0.0.0 then in your Dockerfile, add the lines:
|
@natekupp Full working demo for scheduler: |
I use
dagster schedule start --start-all
inside docker container for script in docs https://dagster.readthedocs.io/en/0.6.0.post0/sections/learn/tutorial/scheduler.html
Dockerfile:
docker-compose.yml
And get
The text was updated successfully, but these errors were encountered: