# Why is the Docker container installation recommended for imports?

**URL:** <https://meta.discourse.org/t/why-is-the-docker-container-installation-recommended-for-imports/212523>\
**Category:** Product Support\
**Created:** [December 18, 2021, 2:45pm UTC](https://meta.discourse.org/t/why-is-the-docker-container-installation-recommended-for-imports/212523 "2021-12-18T14:45:50Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)\
**Post date:** [December 19, 2021, 1:36am UTC](https://meta.discourse.org/t/why-is-the-docker-container-installation-recommended-for-imports/212523/3 "2021-12-19T01:36:35Z")

</div>

Mostly for the same reason we only support our Docker based setup when you install Discourse. We can’t really help you when we don’t know how the development environmental was set up. There’s simply too much that could go wrong. Different Ruby version, wrong version of ImageMagick, missing tools used for image processing,…

I can only speak for myself, but I run all migrations in a Docker container. I use my development environmental only for tweaking an existing script or developing a new one.

---

_[View the full topic](https://meta.discourse.org/t/why-is-the-docker-container-installation-recommended-for-imports/212523)._
