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

Yes it is expected that both of those would resolve.

<@U02J3T6A8LB> thanks for the response. Only one of the values propagates, while both containers spin up prior to the one that is assigned these environment variables. What are the best next steps in debugging this?

I'd check the state of both resources via `pulumi stack export` to see if the output value is filled in for the resource.

<@U02J3T6A8LB> from the `pulumi stack export` we can see that Apply call is being made, yet networkName is null. See this output from that variable:
```"ACCOUNTS_DB_HOSTNAME=",```
That would only be set if the Apply call was invoked, yet the value should come from the parameter being fed in via the Apply:
```var accountsPostgresHostname = accountsPostgresContainer.Hostname.Apply(networkName =&gt; $"ACCOUNTS_DB_HOSTNAME={networkName}");```

<@U02J3T6A8LB> Just an update for anyone else running into this. I had to `pulumi rm` the entire stack and recreate locally for this to work as expected. Not sure what state the local containers go into (considering they were being recreated) however after doing so, both hostnames populate as expected.

Hmm sounds like a provider bug. If you hit this again can you raise a bug on the docker provider repo.