Pre-deployment command fails: 'Could not find a valid container'

[ton77v]

Problem

Pre-deployment commands randomly fail with:

Could not find a valid container. Is the container name correct?

This happens intermittently on both PR preview deployments and main branch deployments.

Workaround

Removing the pre-deployment command resolves the issue.

Environment

• Coolify Cloud (v4.0.0-beta.468)
• Docker compose deployments via github app
• Occurs on both PR preview and main branch deployments

🦀 sent by Claude Code

[coderabbitai]

🔗 Related PRs

#4771 - fix: pull latest image from registry when using build server [merged]
#7460 - fix: prevent cleanup exceptions from marking successful deployments as failed [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[Cinzya]

@ton77v what Coolify version are you on? Does latest mean 469?

Also we prefer if you / your LLM use the issue templates we have set up. As it prompts you to provide additional information which is missing now.

[dominiccarrington61-a11y]

Confirmed same behavior observed here

…

On Sun, Mar 22, 2026, 4:10 AM Cynthia Ebert ***@***.***> wrote: *Cinzya* left a comment (coollabsio/coolify#9076) <#9076 (comment)> @ton77v <https://github.com/ton77v> what Coolify version are you on? Also we prefer if you / your LLM use the issue templates we have set up. As it prompts you to provide additional information which is missing now. — Reply to this email directly, view it on GitHub <#9076?email_source=notifications&email_token=B74GC3HWL7JKPDWMRIMAOS34R6UXRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJQGU4DKNZWG422M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4105857675>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B74GC3BVAT7ME3OAUHTHXDL4R6UXRAVCNFSM6AAAAACW2RTND2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMBVHA2TONRXGU> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[ton77v]

@ton77v what Coolify version are you on? Does latest mean 469?

Coolify Cloud, so the latest is v4.0.0-beta.468

Also we prefer if you / your LLM use the issue templates we have set up. As it prompts you to provide additional information which is missing now.

Sorry about that, next time they should use the proper template and not infer "self-hosted"