You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Steps to Reproduce
Create an app using coolify like nginx:latest
Start the app
Create a scheduled task like echo "hello" on * * * * *
You'll see that the executions are working
Add an healthchecks with a 100s start period (only needed to make the issue more easier to reproduce)
hit redeploy, for 100s you'll have two container (you can see that in the logs tab)
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.
The text was updated successfully, but these errors were encountered:
Vahor
added
🐛 Bug
Reported issues that need to be reproduced by the team.
🔍 Triage
Issues that need assessment and prioritization.
labels
Sep 20, 2024
Error Message and Logs
Maybe without luck but a scheduled task ran at the same time when I redeployed my app.
Steps to Reproduce
echo "hello"
on* * * * *
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.
The text was updated successfully, but these errors were encountered: