You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2018. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: