# Deploy blocked due to "2 different images in your app"

**URL:** <https://community.fly.io/t/deploy-blocked-due-to-2-different-images-in-your-app/23875>\
**Category:** General\
**Tags:** machines, registry, login-only\
**Created:** [February 13, 2025, 8:39am UTC](https://community.fly.io/t/deploy-blocked-due-to-2-different-images-in-your-app/23875 "2025-02-13T08:39:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![eugene-b](https://avatars.discourse-cdn.com/v4/letter/e/b4bc9f/32.png) [@eugene-b](https://community.fly.io/u/eugene-b)\
**Post date:** [February 13, 2025, 8:39am UTC](https://community.fly.io/t/deploy-blocked-due-to-2-different-images-in-your-app/23875/1 "2025-02-13T08:39:46Z")

</div>

We are facing issue when a deploy is blocked due to

`Found 2 different images in your app (for bluegreen to work, all machines need to run a single image)`

This usually happens when we deploy after cancelling previous github CI/CD build. Or when trying to deploy multiple builds without waiting previous one to finish.

It looks like it is a valid behavior [Improved bluegreen deployments](https://community.fly.io/t/improved-bluegreen-deployments/19472)

So the question is - How to configure our deployment process to prevent this “blocking” issue, especially when deploying multiple builds at the same time?

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/fly1/original/3X/6/e/6e8955d00cb218e186ebbe3a6ab06fefdce15290.svg) [@system](https://community.fly.io/u/system)\
**Post date:** [February 20, 2025, 8:40am UTC](https://community.fly.io/t/deploy-blocked-due-to-2-different-images-in-your-app/23875/2 "2025-02-20T08:40:44Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.