# 이미지를 불러올 수 없습니다: “Uncaught (in promise) no-response: no-response”

**URL:** https://meta.discourse.org/t/cannot-load-any-images-uncaught-in-promise-no-response-no-response/273436
**Category:** Self-hosting
**Tags:** dev-install
**Created:** [8월 1, 2023, 5:36오전 UTC](https://meta.discourse.org/t/cannot-load-any-images-uncaught-in-promise-no-response-no-response/273436 "2023-08-01T05:36:41Z")
**Posts on this page:** 1
**Showing post:** 11

<div class="post-metadata">

### Author: ![wayway\_way](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/wayway_way/32/327018_2.png) [@wayway\_way](https://meta.discourse.org/u/wayway_way)
#### Post date: [9월 15, 2023, 8:42오전 UTC](https://meta.discourse.org/t/cannot-load-any-images-uncaught-in-promise-no-response-no-response/273436/11 "2023-09-15T08:42:59Z")

</div>

아래 링크에 따라 설치하셨다면

> [@Install Discourse for development using Docker](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009):
>
> Developing using Docker Since Discourse runs in Docker, you should be able to run Discourse directly from your source directory using a Discourse development container. white_check_mark Pros: No need to install any system dependencies, no configuration needed at all for setting up a development environment quickly. x Cons: Will be slightly slower than the native dev environment on Ubuntu, and much slower than a native install on MacOS. See also [Developing Discourse using a Dev Container](https://meta.discourse.org/t/developing-discourse-using-a-dev-container/336366) …

가상 머신을 다시 열 때마다 프로젝트 루트 디렉터리에서 다음 명령을 실행할 수 있을 것 같습니다:

```plaintext
# 하나의 터미널에서:
d/rails s

# 그리고 별도의 터미널에서
d/ember-cli

```

---

_[View the full topic](https://meta.discourse.org/t/cannot-load-any-images-uncaught-in-promise-no-response-no-response/273436)._