These are chat archives for apparatus/fuge

13th
May 2016
Jun Matsushita
@jmatsushita
May 13 2016 15:46
Hi @AdrianRossouw I ran into the same problem than @ilyaigpetrov but in my case running fuge shell ./fuge/compose-dev.yml did work. It seems that processes run fine as node but I can't find how to (or figure out if fuge is meant to) run services locally as docker containers. I assume the runDocker config key is for adding other services, but I assumed it would be useful to use fuge to also test a docker compose deployment.
Maybe I just need to add the images names after building them with docker-compose build in the docker-compose.yml file? Or docker run as the defaults.run command in fuge-config.js ?
Jun Matsushita
@jmatsushita
May 13 2016 15:56
Adding fuge_* image names and changing runDocker to true does seem to bring up the docker services into the fuge shell but starting them bumps into a hapi error about a missing port. I guess I'm on the right path though...
Jun Matsushita
@jmatsushita
May 13 2016 16:07

I think the error comes from the fact that apparently ENV variables are not passed to docker run. Instead something strange happens with the 10000 variable being set to 20000 :)

running: PROXY_HOST=127.0.0.1 SERVICE_HOST=0.0.0.0 frontend_PORT=10000 api_PORT=10001 service1_PORT=10002 service2_PORT=10003 SERVICE_PORT=20000 SERVICE_HOST=0.0.0.0 SERVICE_PORT=20000 PROXY_HOST=192.168.99.100 frontend_PORT=10000 api_PORT=10001 service1_PORT=10002 service2_PORT=10003 exec docker run --name frontend -p 10000:20000 -e 10000=20000 fuge_frontend

Maybe related to #18