# Docker-compose v2 {{.Name}} structures \<No Value\>

**URL:** <https://forums.docker.com/t/docker-compose-v2-name-structures-no-value/74511>\
**Category:** Compose\
**Created:** [May 8, 2019, 9:31am UTC](https://forums.docker.com/t/docker-compose-v2-name-structures-no-value/74511 "2019-05-08T09:31:42Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![sfgreensill](https://avatars.discourse-cdn.com/v4/letter/s/977dab/32.png) [@sfgreensill](https://forums.docker.com/u/sfgreensill)\
**Post date:** [May 8, 2019, 9:31am UTC](https://forums.docker.com/t/docker-compose-v2-name-structures-no-value/74511/1 "2019-05-08T09:31:42Z")

</div>

Hi there,

The issue is that `tag: '{{.Name}}'` does not resolve to a container name.

We use Docker with Rancher and Jenkins. Within this mix we have a problem which has occurred recently.

```auto
    logging:
      driver: awslogs
      options:
        awslogs-region: eu-central-1
        awslogs-group: $LOGGING_CONTEXT-$RANCHER_STACK
        awslogs-create-group: true
        tag: '{{.Name}}'

```

 ![image](https://global.discourse-cdn.com/docker/original/3X/2/c/2c90e733f05bcf8e6286e99e8f8dab467886ecde.png)

The first image is from our docker-compose v2 and the second from our rancher environment. I believe that “tag” should be evaluated to docker’s name for the container before being passed to Rancher.

During initial setup, I experimented with the `tag: '{{.Name}}'` syntax, at the time I found that unique container names weren’t helpful as log names but the syntax did work.

Previously, we were using a hard coded string here but with the move to multiple containers our goal is to generate a tag with a sensible name and some kind or ordinal or distinct identifier.

Any insight or guidance would be gratefully received, thank you.