Skip to content
This repository has been archived by the owner on Dec 13, 2018. It is now read-only.

Not working properly when using compose mode + service with fixed container names #239

Open
blop opened this issue Dec 6, 2017 · 1 comment

Comments

@blop
Copy link

blop commented Dec 6, 2017

If you have one or more services which looks like :
serviceA:
container_name: serviceA

Then dockercloud/haproxy is not looking up the container name correctly and fail to make that backend usable. I guess it expects some standard format like $project_$service_1.

Workaround is to remove explicit container_name entries from yaml project.
This should be fixed, or mentioned in documentation if not.

@mister2d
Copy link

It is mentioned in the documentation. Has been since day one I believe.

  • DO not overwrite HOSTNAME environment variable in dockercloud/haproxy container.
  • The container name is maintained by docker-compose, and used for service discovery as well. Please DO NOT change container_name of the linked service in the compose file to a non-standard name. Otherwise, that service will be ignored.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants