'
bootstrap failed with exit code 1
**FAILED TO BOOTSTRAP** please scroll up and look for earlier error messages, there may be more than one.
```
Any ideas how to fix this? My forum is currently unavailable after this re-deployment š
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [October 4, 2024, 4:15pm UTC](https://meta.discourse.org/t/launcher-fails-line-334-null-byte-ignored/329365/2 "2024-10-04T16:15:47Z")
You should be able to get it back up with
```
./launcher start app
```
That will restart the old container.
I donāt know what the actual problem might be, but it could be a regression.
---
### Author:  [@Thomas\_Rother](https://meta.discourse.org/u/Thomas_Rother)
#### Post date: [October 4, 2024, 4:19pm UTC](https://meta.discourse.org/t/launcher-fails-line-334-null-byte-ignored/329365/3 "2024-10-04T16:19:30Z")
> [@pfaffman](#):
>
> `./launcher start app`
In this case web\_only and data are separated containers and the startup of the web\_only container fails with
```plaintext
oot@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
```
Maybe I need to start manually through docker in this case as the database is external on another machine, see this code in the web\_only yaml:
```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
```
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [October 4, 2024, 5:39pm UTC](https://meta.discourse.org/t/launcher-fails-line-334-null-byte-ignored/329365/4 "2024-10-04T17:39:21Z")
> [@Thomas\_Rother](#):
>
> In this case web\_only and data are separated containers
Sorry. I didnāt know that part (or maybe didnāt read carefully).
Then you need to
```plaintext
./launcher destroy web_only;./launcher start web_only
```
Unless youāve run a cleanup that deleted the container, in which case youāre likely in trouble.
> [@Thomas\_Rother](#):
>
> the database is external on another machine
Then Iām surprised to see the ācannot linkā error. Iāve only seen that when itās trying to use a docker `link` to talk to another container on the same machine.
> [@Thomas\_Rother](#):
>
> ```plaintext
> DISCOURSE_REDIS_HOST: data
>
> ```
Oh! Yeah, itās the redis that it canāt connect to. Youāve got a `data` container with the redis in it, right? The destroy start should work with the given caveat.
---
### Author:  [@Thomas\_Rother](https://meta.discourse.org/u/Thomas_Rother)
#### Post date: [October 4, 2024, 9:26pm UTC](https://meta.discourse.org/t/launcher-fails-line-334-null-byte-ignored/329365/5 "2024-10-04T21:26:53Z")
> [@pfaffman](#):
>
> ```plaintext
> /launcher destroy web_only;./launcher start web_only
>
> ```
@pfaffman thanks, that fixed it. I forgot that the data container also provides the redis caching functionality - but anyway, now the containers are running again.
What can we do with the bootstrap error from launcher script, line 334? I never saw this error before. Is the launcher\_go/v2 ready to use as a replacement instead?
```plaintext
330 set_template_info() {
331 templates=$(find_templates $config_file)
332
333 arrTemplates=(${templates// / })
334 config_data=$(cat $config_file)
335
336 input="hack: true"
337
338 for template in "${arrTemplates[@]}"
339 do
340 [! -z $template] && {
341 input="$input _FILE_SEPERATOR_ $(cat $template)"
342 }
343 done
344
```
---
### Author:  [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [October 4, 2024, 9:34pm UTC](https://meta.discourse.org/t/launcher-fails-line-334-null-byte-ignored/329365/6 "2024-10-04T21:34:04Z")
This is not the error, itās just a warning
> [@Thomas\_Rother](#):
>
> `/launcher: Zeile 334: Warnung: Kommandoersetzung: NULL-Byte in der Eingabe ignoriert`
This is the error.
> [@Thomas\_Rother](#):
>
> ```plaintext
> /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups/cli.rb:54:in `split': invalid byte sequence in UTF-8 (ArgumentError)
>
> split = conf.split("_FILE_SEPERATOR_")
>
> ```
It seems to me your `web-app.yml` might be corrupted.
---
### Author:  [@Thomas\_Rother](https://meta.discourse.org/u/Thomas_Rother)
#### Post date: [October 5, 2024, 5:53am UTC](https://meta.discourse.org/t/launcher-fails-line-334-null-byte-ignored/329365/7 "2024-10-05T05:53:00Z")
yep:
```plaintext
root@docker2:/var/discourse/containers# yamllint web_only.yml
web_only.yml
5:81 error line too long (115 > 80 characters) (line-length)
8:1 warning missing document start "---" (document-start)
14:4 warning missing starting space in comment (comments)
14:3 warning comment not indented like content (comments-indentation)
15:4 warning missing starting space in comment (comments)
18:81 error line too long (85 > 80 characters) (line-length)
36:3 warning comment not indented like content (comments-indentation)
37:4 warning missing starting space in comment (comments)
43:81 error line too long (85 > 80 characters) (line-length)
44:81 error line too long (87 > 80 characters) (line-length)
58:81 error line too long (84 > 80 characters) (line-length)
67:81 error line too long (90 > 80 characters) (line-length)
68:4 warning missing starting space in comment (comments)
77:81 error line too long (83 > 80 characters) (line-length)
79:4 warning missing starting space in comment (comments)
99:81 error line too long (81 > 80 characters) (line-length)
110:81 error line too long (81 > 80 characters) (line-length)
117:81 error line too long (81 > 80 characters) (line-length)
126:43 error trailing spaces (trailing-spaces)
151:4 warning missing starting space in comment (comments)
154:4 warning missing starting space in comment (comments)
155:4 warning missing starting space in comment (comments)
156:4 warning missing starting space in comment (comments)
156:81 error line too long (131 > 80 characters) (line-length)
```
It definitely needs some cleanup š