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
Yesterday I've found that all the deployments (repo- and docker-based) are queued for hours while nothing happens. I've checked the deployments logs and found out that a few days ago one of the deployments just hung after the success e.g.:
2024-Dec-31 05:23:41.358199
Starting pull request (#133) deployment of XXX:main.
...
2024-Dec-31 05:40:36.757449
time="2024-12-31T05:40:36Z" level=warning msg="Found orphan containers ([wgwosgg-041140314269 wgwosgg-pr-132]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up."
2024-Dec-31 05:40:36.775610
Container wgwosgg-pr-133 Creating
2024-Dec-31 05:40:36.856169
wgwosgg-pr-133 Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.
2024-Dec-31 05:40:36.874800
Container wgwosgg-pr-133 Created
2024-Dec-31 05:40:36.874800
Container wgwosgg-pr-133 Starting
2024-Dec-31 05:40:37.154697
Container wgwosgg-pr-133 Started
2024-Dec-31 05:40:37.170425
New container started.
^^^^^^^^^^^^^^ however it was shown as "running for XXX,XXX seconds; the only unusual thing there were the orphans; I've checked they seem to appear the same day
The "Logs" tab, indeed, had two "ghost" PR deployments that were actually closed Dec 31th
There were a couple of other deployments also running for "2 days", "4 days", a couple of successful ones and the rest was just hanging in "queued".
While in the UI I've also noted this message frequently pops: #4309 however I've seen it before
Steps to Reproduce
Unfortunately I've noticed the issue a few days after and can't see what exactly caused that. Orphan containers... ?
Canceling all the pending deployments, stopping the "ghost" containers, running docker prune and restarting the services solved the issue
Example Repository URL
No response
Coolify Version
v4.0.0-beta.380
Are you using Coolify Cloud?
Yes (Coolify Cloud)
Operating System and Version (self-hosted)
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
ton77v
added
🐛 Bug
Reported issues that need to be reproduced by the team.
🔍 Triage
Issues that need assessment and prioritization.
labels
Jan 5, 2025
Error Message and Logs
Yesterday I've found that all the deployments (repo- and docker-based) are queued for hours while nothing happens. I've checked the deployments logs and found out that a few days ago one of the deployments just hung after the success e.g.:
^^^^^^^^^^^^^^ however it was shown as "running for XXX,XXX seconds; the only unusual thing there were the orphans; I've checked they seem to appear the same day
The "Logs" tab, indeed, had two "ghost" PR deployments that were actually closed Dec 31th
There were a couple of other deployments also running for "2 days", "4 days", a couple of successful ones and the rest was just hanging in "queued".
While in the UI I've also noted this message frequently pops: #4309 however I've seen it before
Steps to Reproduce
Unfortunately I've noticed the issue a few days after and can't see what exactly caused that. Orphan containers... ?
Canceling all the pending deployments, stopping the "ghost" containers, running docker prune and restarting the services solved the issue
Example Repository URL
No response
Coolify Version
v4.0.0-beta.380
Are you using Coolify Cloud?
Yes (Coolify Cloud)
Operating System and Version (self-hosted)
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: