How to correctly setup Eclipse Che on Docker Cloud

I’ve just got Che running nicely (all diagnostic tests pass) on Docker Cloud / AWS. I just wanted to check whether we should still be setting CHE_HOST or not with the below config?

Everything seems to work fine without, I just don’t want to slow anything down by external DNS or something happening where I can’t see it.

We have set CHE_DOCKER_IP_EXTERNAL to the FQDN of the container running Che.

che:
  environment:
    - CHE_DOCKER_IP_EXTERNAL=$DOCKERCLOUD_SERVICE_FQDN
    - CHE_DOCKER_SERVER__EVALUATION__STRATEGY=docker-local
#  - CHE_HOST=$DOCKERCLOUD_SERVICE_FQDN
  image: 'eclipse/che-server:5.7.2'
  ports:
    - '8080:8080'
  restart: always
  ...

Oh, and how do CHE_IP and CHE_API come into this? They don’t seem to be necessary even through we are connecting from a remote browser?

[davidwindell]

For those interested, our full stack looks roughly like this:

che-user1:
  environment:
    - CHE_DOCKER_IP_EXTERNAL=$DOCKERCLOUD_SERVICE_FQDN
    - CHE_DOCKER_SERVER__EVALUATION__STRATEGY=docker-local
    - CHE_PORT=80
    - CHE_WORKSPACE_VOLUME=/var/run/docker.sock:/var/run/docker.sock
    - VIRTUAL_HOST=$DOCKERCLOUD_SERVICE_FQDN
  expose:
    - '80'
  image: 'eclipse/che-server:5.7.2'
  restart: always
  volumes:
    - '/var/run/docker.sock:/var/run/docker.sock'
    - '/your/host/data/path:/data'
che-user2:
  ...same as "che-user1" but with a different volume mount
nginx-proxy:
  image: 'jwilder/nginx-proxy:alpine'
  ports:
    - '80:80'
  restart: always
  volumes:
    - '/var/run/docker.sock:/tmp/docker.sock:ro'

This instantly gives us multi-user single-server Che with auth handled via AWS VPC Security Groups (i.e. IP grants).

[TylerJewell]

There shouldn’t be a need to. It is not necessary here.