Skip to content
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

[Bug]: Scheduled task can't find container name when redeploying #3520

Open
Vahor opened this issue Sep 20, 2024 · 0 comments
Open

[Bug]: Scheduled task can't find container name when redeploying #3520

Vahor opened this issue Sep 20, 2024 · 0 comments
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.

Comments

@Vahor
Copy link
Contributor

Vahor commented Sep 20, 2024

Error Message and Logs

Maybe without luck but a scheduled task ran at the same time when I redeployed my app.

ScheduledTaskJob failed: More than one container exists but no container name was provided.
image

Steps to Reproduce

  1. Create an app using coolify like nginx:latest
  2. Start the app
  3. Create a scheduled task like echo "hello" on * * * * *
  4. You'll see that the executions are working
  5. Add an healthchecks with a 100s start period (only needed to make the issue more easier to reproduce)
  6. hit redeploy, for 100s you'll have two container (you can see that in the logs tab)
  7. go back to the scheduled task page, you'll see a failed execution

Example Repository URL

No response

Coolify Version

v4.0.0-beta.341

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

No response

Additional Information

When deploying a docker image, we can't predict the container name.
And using a consistent container name disable the rolling update feature.

Maybe the scheduled task should use the older container, but it might be killed.
And on the other side, using the new one is not perfect either as it might not be ready yet.

@Vahor Vahor added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.
Projects
None yet
Development

No branches or pull requests

1 participant