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

i don't think it's in the provider just yet

It seems like it’s there in 2.5.2, I can instantiate it no issue, just trying to figure out how to build and push an image with it

I thought this might work
```    const containerRegistry = new ocean.ContainerRegistry(name, { name }, defaultOpts);
    const credentials = new ocean.ContainerRegistryDockerCredentials(name, { 
      registryName: name,
      write: true,
    }, defaultOpts);

    this.dockerProvider = new docker.Provider(name, {
      registryAuth: [{
        address: containerRegistry.serverUrl,
        configFileContent: credentials.dockerCredentials,
      }],
    }, defaultOpts);```
and then to use that created provider with a new `docker.Image()`

I did, here’s a gist of it: <https://gist.github.com/timmyers/e1c1ee31a7a85d26229a29ec732b659c>

<@UFM2CJXA5> thank you :pray:  really appreciate it. Though I'm getting `undefined` from `credentials.dockerCredentials.apply((_creds_) =&gt; {`, any clue to what it could be?

Hm, if I move the `ContainerRegistryDockerCredentials` outside of the class I get some data, but not the ones I need

Maybe this is the real error: `error: registry not found: GET <https://api.digitalocean.com/v2/registry>: 404 registry does not exist`

<@U014YTFPGAU> I haven’t looked at this in a while, but I’m actually seeing the same `undefined` now

Ah I think I found the issue here if you’re still dealing with this: <https://github.com/digitalocean/terraform-provider-digitalocean/issues/466>
Adding `expirySeconds: 1576800000` fixes it