# Paramertize Docker Labels?

**URL:** <https://community.traefik.io/t/paramertize-docker-labels/6011>\
**Category:** Traefik v2\
**Tags:** docker-swarm\
**Created:** [May 12, 2020, 1:17pm UTC](https://community.traefik.io/t/paramertize-docker-labels/6011 "2020-05-12T13:17:55Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![chrisbecke](https://sea2.discourse-cdn.com/flex020/user_avatar/community.traefik.io/chrisbecke/32/2042_2.png) [@chrisbecke](https://community.traefik.io/u/chrisbecke)\
**Post date:** [May 12, 2020, 1:17pm UTC](https://community.traefik.io/t/paramertize-docker-labels/6011/1 "2020-05-12T13:17:55Z")

</div>

I am trying to deploy at least two instances of a compose file to a docker swarm - using traefik to route traffic to review apps based onthe commit branch name.

So I add labels like this to the docker compose:

```auto
  service-x:
    deploy:
      labels:
        traefik.enable: true
        traefik.http.routers.review_app.rule: Host("${CI_BRANCH}.${DOMAIN}")
        traefik.http.services.review_app.loadbalancer.server.port: 5000

```

However, traefik sees all of these as a single router (review\_app) even though they all belong to different docker stacks.

How do I possibly deploy one compose file twice, with non conflicting routers?  
And, why is this even an issue? Traefik understands that the "traefik.enable" table belongs to this specific service an no other, so it knows which service and stack its processing labels for.
