No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

:wave: Hi everyone! Can anyone tell me if there is a way to add network aliases to a docker service. I can see that there is a network advanced option for containers but not in services

What's a network alias? You can expose services on whatever host ports you choose. Then you can use load balancers or similar to map DNS names to that particular port on your host.
There's probably other solutions, especially if you're using k8s...

The alias is the network name that other containers use to find the container

not using K8s using a docker swarm

Ah. Doesn't swarm use docker-compose.yml? It's all configured in there.

This should do it: <https://docs.docker.com/compose/compose-file/#networks>

Yes but I am setting everything up through Pulumi without a compose file

the services are replicating over multiple nodes but cannot talk to each other as the aliases are missing

If I manually add these to the hostconfig of the containers all is good

what I really need is access to this `task_spec.networks_advanced`

Looks like service task specs can be provided container specs, that include networkAdvanced aliases...

which brings us back to the original question of how to add this in a service not a container

terraform has it for both by the looks of it

Maybe it's missing from the docs only? The SDK is built from the Terraform schema, so it should match...

pulumi has this

<https://www.pulumi.com/registry/packages/docker/api-docs/service/#networks_csharp|Networks>List&lt;string&gt;