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:
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?