Skip to content
This repository was archived by the owner on Dec 13, 2018. It is now read-only.
This repository was 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

Description

@blop

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.

Activity

  1. mister2d commented on Dec 21, 2017

    @mister2d

    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 join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions