# Metadata and net:container vs deployment unit

**URL:** <https://forums.suse.com/t/metadata-and-net-container-vs-deployment-unit/3587>\
**Category:** General\
**Created:** [July 30, 2016, 8:32am UTC](https://forums.suse.com/t/metadata-and-net-container-vs-deployment-unit/3587 "2016-07-30T08:32:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![blaggacao](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/blaggacao/32/531_2.png) [@blaggacao](https://forums.suse.com/u/blaggacao)\
**Post date:** [July 30, 2016, 8:32am UTC](https://forums.suse.com/t/metadata-and-net-container-vs-deployment-unit/3587/1 "2016-07-30T08:32:21Z")

</div>

In the following part of the catalogue, I use confd in the -config image.  
I copied that more or less from the elasticsearch example and am trying to sort things out…

To start I have a couple of questions:

1. What is the role of net: “container:telegraf-config” ? Can I drop it?
2. Can be confirmed, that the deployment unit concept is responsible for that custom metadata, while defined only on telegraf service is shared with telegraf-config service?

```auto
telegraf-config:
  image: registry.devco.co/telegraf-config:1.0.0

telegraf:
  net: "container:telegraf-config"
  image: registry.devco.co/telegraf:1.0.0-beta3-alpine
  volumes_from:
    - telegraf-config
  links:
    - influxdb
  ports:
    - "8092:8092/udp"
    - "8094:8094"
    - "8125:8125/udp"
  labels:
    io.rancher.scheduler.global: 'true'
    io.rancher.sidekicks: telegraf-config

```