# Il launcher fallisce: linea 334: byte NULL ignorato

**URL:** <https://meta.discourse.org/t/launcher-fails-line-334-null-byte-ignored/329365>\
**Category:** Self-hosting\
**Created:** [4 Ottobre 2024, 4:07pm UTC](https://meta.discourse.org/t/launcher-fails-line-334-null-byte-ignored/329365 "2024-10-04T16:07:26Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Thomas\_Rother](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/thomas_rother/32/423597_2.png) [@Thomas\_Rother](https://meta.discourse.org/u/Thomas_Rother)\
**Post date:** [4 Ottobre 2024, 4:19pm UTC](https://meta.discourse.org/t/launcher-fails-line-334-null-byte-ignored/329365/3 "2024-10-04T16:19:30Z")

</div>

> [@pfaffman](#):
>
> `./launcher start app`

In questo caso web\_only e data sono container separati e l’avvio del container web\_only fallisce con

```plaintext
root@docker2:/var/discourse# ./launcher start web_only
x86_64 arch detected.

starting up existing container
+ /usr/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

```

Forse in questo caso devo avviare manualmente tramite docker poiché il database è esterno su un’altra macchina, vedi questo codice nello yaml di web\_only:

```plaintext
 ## connect to central postgres database
  DISCOURSE_DB_SOCKET: ''
  DISCOURSE_DB_USERNAME: discourse
  DISCOURSE_DB_PASSWORD: xxxxxxxxxx
  DISCOURSE_DB_HOST: 10.10.xx.xx
  DISCOURSE_REDIS_HOST: data

```

---

_[View the full topic](https://meta.discourse.org/t/launcher-fails-line-334-null-byte-ignored/329365)._
