This message was deleted.

sparse-intern-71089

02/12/2022, 12:04 AM

This message was deleted.

echoing-dinner-19531

02/12/2022, 10:40 AM

Yes it is expected that both of those would resolve.

clever-glass-42863

02/12/2022, 2:29 PM

@echoing-dinner-19531 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?

echoing-dinner-19531

02/12/2022, 6:35 PM

I'd check the state of both resources via

pulumi stack export

to see if the output value is filled in for the resource.

clever-glass-42863

02/12/2022, 7:47 PM

@echoing-dinner-19531 from the

pulumi stack export

we can see that Apply call is being made, yet networkName is null. See this output from that variable:

Copy code

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

Copy code

var accountsPostgresHostname = accountsPostgresContainer.Hostname.Apply(networkName => $"ACCOUNTS_DB_HOSTNAME={networkName}");

clever-glass-42863

02/12/2022, 8:37 PM

@echoing-dinner-19531 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.

echoing-dinner-19531

02/12/2022, 8:52 PM

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

✅ 1

3 Views

Open in Slack

Previous Next

Pulumi Community

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.