Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Schedule exited containers #25
I see this in the log:
2017-08-28 09:38:59,967|INFO |Locking service id: xxxyyy 2017-08-28 09:38:59,970|INFO |Added 'scheduled' for demo 2017-08-28 09:39:11,648|INFO |Unlocking service id: xxxyyy 2017-08-28 09:39:11,838|INFO |Removing job 'scheduled' for demo
The demo container runs a single command and then exits, so it is in Exited(0) state. Is it then correctly understood that I can't have deck-chore run the container when exited? Would it be possible to add an option to have it start the container?
i'm not sure, whether i'm understanding the scenario. more details would be helpful.
no, deck-chores does not control containers. it just observes them and executes commands within containers.
I realized that I then need docker compose to run the container with a command like ```bash tail -f /dev/null ``` To start the container and keep it running, while I'll let the deck-chores run the scheduled command.…
On Mon, 28 Aug 2017, 13:48 Frank Sachsenheim ***@***.***> wrote: i'm not sure, whether i'm understanding the scenario. more details would be helpful. Is it then correctly understood that I can't have deck-chore run the container when exited? no, deck-chores does not control containers. it just observes them and executes commands *within* containers. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABkQ_N0AOqsiu4gx8dOvunnDOhbxl8ERks5scqkcgaJpZM4PEUkV> .