https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
b
i don't think it's in the provider just yet
m
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
Copy code
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()
d
@millions-judge-24978 did you get it to work?
m
d
@millions-judge-24978 thank you 🙏 really appreciate it. Though I'm getting 
undefined
from 
credentials.dockerCredentials.apply((_creds_) => {
, 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
m
@dazzling-sundown-39670 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
Open in Slack
PreviousNext
Powered by

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.

Powered by