polite-umbrella-11196
04/09/2023, 4:44 PMerror: error: invalid reference format. This provider requires all image names to be fully qualified.
For example, if you are attempting to push to Dockerhub, prefix your image name with `<http://docker.io|docker.io>`:
`<http://docker.io/repository/image:tag|docker.io/repository/image:tag>`
(I’m migrating from old tech, so I don’t know what I’m doing wrong).
Technical details in 🧵const createImage = (registryId: pulumi.Output<string>) => {
const registryToken = aws.ecr.getAuthorizationTokenOutput({ registryId });
return registryToken.apply((registry) => {
const recorderImage = new docker.Image('recorder', {
imageName: `${imageName}:${imageVersion}`,
build: {
context: SERVICE_PATH,
platform: 'linux/amd64',
},
registry,
});
return recorderImage.imageName;
});
};
For imageName
I’ve tried:
• registry.proxyEndpoint
• ``${registry.proxyEndpoint}/${imageName}:${imageVersion}``
• ``${imageName}:${imageVersion}``
None of them worked.brainy-church-78120
04/09/2023, 5:19 PMpolite-umbrella-11196
04/09/2023, 5:23 PMhttps://
off of the registry.proxyEndpoint
and use that like so:
<http://111111111111.dkr.ecr.us-west-1.amazonaws.com/recorder:1.0.21|111111111111.dkr.ecr.us-west-1.amazonaws.com/recorder:1.0.21>
then it goes on, but now it’s seems to be failing with credentials being wrong.
I’m trying this:
registry: {
server: '<http://111111111111.dkr.ecr.us-west-1.amazonaws.com|111111111111.dkr.ecr.us-west-1.amazonaws.com>',
username: 'AWS',
password: registry.password,
},
Does that look right?/recorder
on to the end of server to see if that made a difference, negative.cuddly-flower-91328
04/10/2023, 1:37 AMawsx.ecr
for repository and image to build and push. Not sure if that’s helpful but it’s working for us.polite-umbrella-11196
04/10/2023, 1:38 AMsalmon-account-74572
04/10/2023, 2:00 PM