Scheduled tasks on ephemeral containers
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
In my team we have a set of dockerized CLIs that we would like to move over to dokploy, both for deployment purposes and scheduling.
The issue is that when deploying a CLI on Dokploy, the container will exit automatically.
When creating a Schedule, we cannot run it on the created container because it has exited, so our only option is to create a Gobal schedule that does docker run --rm -e <Env1> -e <Env2> <image> <command>, repeating all the configured environment that we have in the Dokploy project.
Describe the solution you'd like
Some way to automatically do this docker run --rm with a specific command inside a project Schedule
Describe alternatives you've considered
The "manual" docker run command, which defeats the purpose of managing environments in Dokploy
Additional context
No response
Will you send a PR to implement it?
No
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how project Schedules select and execute containers, then compare that flow with the described docker run --rm command for an exited CLI container. Done means a project Schedule can run the configured image with its project environment and a specified command without requiring a separate global schedule.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100