# Cannot link to a non running container: /data AS /web\_only/data

**URL:** https://meta.discourse.org/t/cannot-link-to-a-non-running-container-data-as-web-only-data/163565
**Category:** Support
**Created:** [September 10, 2020, 12:47am UTC](https://meta.discourse.org/t/cannot-link-to-a-non-running-container-data-as-web-only-data/163565 "2020-09-10T00:47:38Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![csmu](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/csmu/32/124581_2.png) [@csmu](https://meta.discourse.org/u/csmu)
#### Post date: [September 10, 2020, 12:47am UTC](https://meta.discourse.org/t/cannot-link-to-a-non-running-container-data-as-web-only-data/163565/1 "2020-09-10T00:47:38Z")

</div>

We’ve just dated from version 4.2 to the latest version.  
We run a data container and web container.  
Now discourse is not booting with the following error.

```plaintext
[root@sydney discourse]# ./launcher start web_only

starting up existing container
+ /bin/docker start web_only
Error response from daemon: Cannot link to a non running container: /data AS /web_only/data
Error: failed to start containers: web_only

```

Any ideas on how to resolve this?

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [September 10, 2020, 1:03am UTC](https://meta.discourse.org/t/cannot-link-to-a-non-running-container-data-as-web-only-data/163565/2 "2020-09-10T01:03:16Z")

</div>

Well, it says data is not running… Try running this:

```plaintext
./launcher rebuild data
./launcher rebuild web_only

```

---

<div class="post-metadata">

### Author: ![csmu](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/csmu/32/124581_2.png) [@csmu](https://meta.discourse.org/u/csmu)
#### Post date: [September 10, 2020, 2:18am UTC](https://meta.discourse.org/t/cannot-link-to-a-non-running-container-data-as-web-only-data/163565/3 "2020-09-10T02:18:07Z")

</div>

> [@riking](#):
>
> Well, it says data is not running… Try running this:

data is running.

```plaintext
[root@sydney discourse]# docker ps | grep data
860547699a11 local_discourse/data "/sbin/boot" 2 hours ago Up 2 hours     

```

Maybe renaming the reference in the docker image from local\_discourse/data to web\_only/data would cut it.

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [September 10, 2020, 2:18am UTC](https://meta.discourse.org/t/cannot-link-to-a-non-running-container-data-as-web-only-data/163565/4 "2020-09-10T02:18:58Z")

</div>

In that case, re-check all references to data from the `web_only.yml` file.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [September 10, 2020, 4:51pm UTC](https://meta.discourse.org/t/cannot-link-to-a-non-running-container-data-as-web-only-data/163565/5 "2020-09-10T16:51:22Z")

</div>

I think this happens if you rebuild the data container and start up a new one. Even though it’s still named data, the running web container is still looking for the old one. I think this should do it:

```plaintext
./launcher stop web_only
./launcher destroy web_only
./launcher start web_only

```

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [October 10, 2020, 4:59pm UTC](https://meta.discourse.org/t/cannot-link-to-a-non-running-container-data-as-web-only-data/163565/6 "2020-10-10T16:59:57Z")

</div>

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