# בונה תמונות Discourse עבור צינורות Gitlab CI/CD

**URL:** <https://meta.discourse.org/t/discourse-image-builder-for-gitlab-ci-cd-pipelines/261857>\
**Category:** Self-hosting\
**Tags:** unsupported-install\
**Created:** [16 באפריל,‏ 2023,‏ 12:44pm UTC](https://meta.discourse.org/t/discourse-image-builder-for-gitlab-ci-cd-pipelines/261857 "2023-04-16T12:44:10Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![mkbrechtel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mkbrechtel/32/295242_2.png) [@mkbrechtel](https://meta.discourse.org/u/mkbrechtel)\
**Post date:** [16 באפריל,‏ 2023,‏ 9:10pm UTC](https://meta.discourse.org/t/discourse-image-builder-for-gitlab-ci-cd-pipelines/261857/5 "2023-04-16T21:10:55Z")

</div>

> [@Falco](#):
>
> There is a `version` parameter on the app.yml file that can be set to the version you want to run.

We tried that to create a deployment from 2.8, but it fails complaining about a wrong Discourse version. Since we can now reproduce this in our CI/CD you can look at the error here: [docker-build (#4121616927) · Jobs · idcohorts / RPS / Discourse Image Builder · GitLab](https://gitlab.com/idcohorts/rps/discourse-image-builder/-/jobs/4121616927#L160)

> [@Falco](#):
>
> Using the [official install](https://meta.discourse.org/t/142537?silent=true) that is handled using Move from standalone container to separate web and data containers.

> [@Falco](#):
>
> Yes, the launcher based flow is not compatible out-of-the-box with container orchestration. That said, it can be made compatible by running `./launcher bootstrap app` and pushing the resulting image to a container registry and then running said image via orchestration.

That’s what we are doing basically. 🙂

> [@Falco](#):
>
> We welcome a pull request to make this possible, as it sounds useful generally. #pr-welcome

Thank you, on it.

---

_[View the full topic](https://meta.discourse.org/t/discourse-image-builder-for-gitlab-ci-cd-pipelines/261857)._