# Docker compose and managed network

**URL:** https://forums.suse.com/t/docker-compose-and-managed-network/10665
**Category:** Rancher 1.x
**Created:** [June 5, 2018, 6:58am UTC](https://forums.suse.com/t/docker-compose-and-managed-network/10665 "2018-06-05T06:58:34Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![pdonorio](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/pdonorio/32/3089_2.png) [@pdonorio](https://forums.suse.com/u/pdonorio)
#### Post date: [June 5, 2018, 6:58am UTC](https://forums.suse.com/t/docker-compose-and-managed-network/10665/1 "2018-06-05T06:58:34Z")

</div>

Hello there,  
I’ve seen a strange problem on networking with normal containers launched inside rancher nodes.

I want the container to see the others in other nodes so as stated in the doc I add the dedicated label, e.g.:

`docker run --rm -it --label io.rancher.container.network=true alpine ash`  
This works and I get an IP assigned inside the `managed` rancher network.

But, if I switch to do the same exact thing on docker-compose:

```auto
version: '3'
services:
  tmp:
    image: alpine
    command: sleep 123456789
    labels:
      io.rancher.container.network: true

```

This doesn’t give errors but the container IP is not managed by rancher.  
Anyone any clue? 🤔