# Launcher always exits with "ERROR: Config name must not contain upper case characters, spaces or special characters."

**URL:** https://meta.discourse.org/t/launcher-always-exits-with-error-config-name-must-not-contain-upper-case-characters-spaces-or-special-characters/49642
**Category:** Self-hosting
**Created:** [2 september 2016 om 18:50 UTC](https://meta.discourse.org/t/launcher-always-exits-with-error-config-name-must-not-contain-upper-case-characters-spaces-or-special-characters/49642 "2016-09-02T18:50:48Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![jako512](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jako512/32/120818_2.png) [@jako512](https://meta.discourse.org/u/jako512)
#### Post date: [2 september 2016 om 18:50 UTC](https://meta.discourse.org/t/launcher-always-exits-with-error-config-name-must-not-contain-upper-case-characters-spaces-or-special-characters/49642/1 "2016-09-02T18:50:48Z")

</div>

No matter what any launcher command “`./launcher * app`” exits with “`ERROR: Config name must not contain upper case characters, spaces or special characters. Correct config name and rerun ./launcher.`”  
I always have to comment “`exit 1`” in this condition… it’s quite annoying…

---

<div class="post-metadata">

### Author: ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [2 september 2016 om 19:00 UTC](https://meta.discourse.org/t/launcher-always-exits-with-error-config-name-must-not-contain-upper-case-characters-spaces-or-special-characters/49642/2 "2016-09-02T19:00:54Z")

</div>

Can you post one concrete call to `launcher` that does this for you?

---

<div class="post-metadata">

### Author: ![jako512](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jako512/32/120818_2.png) [@jako512](https://meta.discourse.org/u/jako512)
#### Post date: [3 september 2016 om 11:49 UTC](https://meta.discourse.org/t/launcher-always-exits-with-error-config-name-must-not-contain-upper-case-characters-spaces-or-special-characters/49642/3 "2016-09-03T11:49:12Z")

</div>

All calls does it:

```
./launcher bootstrap app
./launcher start app
./launcher enter app
./launcher rebuild app

```

The following trimmed script does it too:

```plaintext
#!/bin/bash
re='[A-Z/ !@#$%^&*()+~`=]'
if [[$1 =~ $re]];
  then
    echo "ERROR: Config name must not contain upper case characters, spaces or special characters. Correct config name and rerun $0."
fi

```

---

<div class="post-metadata">

### Author: ![jako512](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jako512/32/120818_2.png) [@jako512](https://meta.discourse.org/u/jako512)
#### Post date: [3 september 2016 om 12:06 UTC](https://meta.discourse.org/t/launcher-always-exits-with-error-config-name-must-not-contain-upper-case-characters-spaces-or-special-characters/49642/4 "2016-09-03T12:06:43Z")

</div>

I believe condition is somehow case insensitive however `shopt nocasematch` is disabled.  
I tried it on clean ubuntu 14.04.3

---

<div class="post-metadata">

### Author: ![Overgrow](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/overgrow/32/478189_2.png) [@Overgrow](https://meta.discourse.org/u/Overgrow)
#### Post date: [17 oktober 2016 om 11:39 UTC](https://meta.discourse.org/t/launcher-always-exits-with-error-config-name-must-not-contain-upper-case-characters-spaces-or-special-characters/49642/5 "2016-10-17T11:39:08Z")

</div>

I’ve got same problem when testing docker on Ubuntu 14.04.4

```
root@og:/var/discourse# lsb_release -a
Description: Ubuntu 14.04.4 LTS

root@og:/var/discourse# ./launcher rebuild app

ERROR: Config name must not contain upper case characters, spaces or special characters. Correct config name and rerun ./launcher.

```

---

<div class="post-metadata">

### Author: ![jako512](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jako512/32/120818_2.png) [@jako512](https://meta.discourse.org/u/jako512)
#### Post date: [5 november 2016 om 12:12 UTC](https://meta.discourse.org/t/launcher-always-exits-with-error-config-name-must-not-contain-upper-case-characters-spaces-or-special-characters/49642/6 "2016-11-05T12:12:28Z")

</div>

The problem is related to locale.  
Everything works as expected until I change the locale.  
Try execute this before launcher:

```plaintext
locale-gen sk_SK.UTF-8
export LANG=sk_SK.UTF-8

```

---

<div class="post-metadata">

### Author: ![otlet](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/otlet/32/71975_2.png) [@otlet](https://meta.discourse.org/u/otlet)
#### Post date: [10 mei 2017 om 21:24 UTC](https://meta.discourse.org/t/launcher-always-exits-with-error-config-name-must-not-contain-upper-case-characters-spaces-or-special-characters/49642/7 "2017-05-10T21:24:34Z")

</div>

I had this same problem on CentOS7

```
localectl set-locale LANG=en_US.utf8

```

I do this and still don’t work. I have no idea what can i do now? Some ideas?

---

<div class="post-metadata">

### Author: ![elijah](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/elijah/32/104055_2.png) [@elijah](https://meta.discourse.org/u/elijah)
#### Post date: [10 mei 2017 om 23:30 UTC](https://meta.discourse.org/t/launcher-always-exits-with-error-config-name-must-not-contain-upper-case-characters-spaces-or-special-characters/49642/8 "2017-05-10T23:30:36Z")

</div>

Did you also `export LANG=en_US.utf8` before running it? The current shell could have it’s own independent idea of locale.

As a separate matter, the test could be rewritten to be less locale sensitive:

```plaintext
#!/bin/bash
re='[^abcdefghijklmnopqrstuvwxyz0123456789_.-]'
if [[$1 =~ $re]];
  then
      echo "ERROR: Config name must not contain upper case characters, spaces or special characters. Correct config name and rerun $0."
fi

```

But maybe people wanted `[configname]` to work…
