Arf … i’m so dumb
I started to explore rancher, coming from tutum… and didn’t get any container when was in that UI so i guess it didn’t showed up in the dropdown
Hey @vincent actually there is a bug
The only way to get this is by adding a container manually from the infrastructure. That option is not available when you try to add a service on an existing stack.
I just realized that when i used rancher-compose to push my yml file that included the net: ‘container:container_name’
I’m on rancher/server:v0.32.0
Looks like a bug…
Not a bug, but a feature not in the UI yet. Creating a service (with scale probably > 1) and linking it to networking for a single container doesn’t really make any sense, so it is hidden on services.
To have multiple services share the same networking (…or volumes) they need to be defined as “sidekicks”; So there is a primary service and one or more related sidekick containers which are always deployed with the same scale and scheduled together with the primary. Creating these is currently only available through rancher-compose: http://docs.rancher.com/rancher/rancher-compose/#sidekicks
@denise@vincent
We need to add a service / container to anothers container netns like done with --network container:<container_name>. The scale should be one. Is there a way to activate it during compose deployment?
Will sidekick do the same? Is it possible to create a multi host sidekick / --network container:<container_name> with rancher?