# Compatibilità del ramo stabile con discourse\_docker e plugin

**URL:** https://meta.discourse.org/t/stable-branch-compatibility-with-discourse-docker-and-plugins/117679
**Category:** Self-hosting
**Tags:** stable
**Created:** [14 Maggio 2019, 10:54am UTC](https://meta.discourse.org/t/stable-branch-compatibility-with-discourse-docker-and-plugins/117679 "2019-05-14T10:54:51Z")
**Posts on this page:** 1
**Showing post:** 19

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [14 Maggio 2019, 1:19pm UTC](https://meta.discourse.org/t/stable-branch-compatibility-with-discourse-docker-and-plugins/117679/19 "2019-05-14T13:19:44Z")

</div>

Thanks for the feedback @spajus. It’s always good if we can find **specific** tasks to improve the experience for users and administrators. Generalising things in one large topic makes it difficult to turn them into actionable tasks.

Looking specifically at your second bullet point. We aim for discourse\_docker to be compatible with the latest `stable`. Are you seeing something different?

> [@Stephen](#):
>
> For the mini-racer issue, it’s being investigated, but for now you can simply:
> 
> ```plaintext
> 
> ```

As far as I know, [this should be resolved](https://meta.discourse.org/t/failing-to-rebuild-app-on-discourse-since-may-7/117121/13) and is no longer being investigated. If it’s still broken, let us know. The `sed` fix is a bad idea, as it will probably break more things in future.

If chef is only provisioning an OS, and you are using `discourse_docker`, then it does seem unlikely that chef is causing the issues.

---

_[View the full topic](https://meta.discourse.org/t/stable-branch-compatibility-with-discourse-docker-and-plugins/117679)._