euphoria-io / heim

A real-time community platform.
https://euphoria.io
Other
874 stars 47 forks source link

Can't setup dev env - `Invalid service name "backend_etcd"`. #83

Open deanrather opened 8 years ago

deanrather commented 8 years ago

Couldn't follow setup steps w/ error: Invalid service name "backend_etcd".

✗ dean@dean-XPS-8700:~$ git clone git@github.com:deanrather/heim.git
...
✓ dean@dean-XPS-8700:~$ sudo apt-get install -y docker
...
✓ dean@dean-XPS-8700:~$ sudo apt-get install -y docker-compose 
...
✓ dean@dean-XPS-8700:~$ cd heim/
✓ dean@dean-XPS-8700:~/heim master$ git submodule update --init
Submodule 'deps' (https://github.com/euphoria-io/heim-deps.git) registered for path '_deps'
Cloning into '_deps'...
remote: Counting objects: 29051, done.
remote: Total 29051 (delta 0), reused 0 (delta 0), pack-reused 29051
Receiving objects: 100% (29051/29051), 65.62 MiB | 276.00 KiB/s, done.
Resolving deltas: 100% (10345/10345), done.
Checking connectivity... done.
Submodule path '_deps': checked out '6158ad0fdabc607e6e7e370235017102c8fffcc8'
✓ dean@dean-XPS-8700:~/heim master$ docker-compose run frontend
Invalid service name "backend_etcd" - only [a-zA-Z0-9] are allowed
✗ dean@dean-XPS-8700:~/heim master$ docker-compose run upgradedb sql-migrate up
Invalid service name "backend_etcd" - only [a-zA-Z0-9] are allowed
✗ dean@dean-XPS-8700:~/heim master$ docker-compose up backend
Invalid service name "backend_etcd" - only [a-zA-Z0-9] are allowed
✗ dean@dean-XPS-8700:~/heim master$ docker-compose run --service-ports frontend gulp develop
Invalid service name "backend_etcd" - only [a-zA-Z0-9] are allowed
✗ dean@dean-XPS-8700:~/heim master$ git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
✓ dean@dean-XPS-8700:~/heim master$ git log -n 1
commit 5246184464a2fe6918677e855f308e2e0c7589da
Author: Logan Hanks <logan.hanks@gmail.com>
Date:   Mon Mar 28 15:33:03 2016 -0700

    Sponsorship
✓ dean@dean-XPS-8700:~/heim master$
ckingdev commented 8 years ago

It looks like there's a bug with docker 1.3. Can you try installing the latest docker version?