trigger base image updates after using az acr import

[Stijnc]

When importing images from mcr or docker hub I want to be able to trigger base image updates. Maybe this is already possible, but I failed. Any pointers are appreciated.

Something in the lines of:

1. import an image from an external repository

 az acr import --name <registryName>--source docker.io/library/<name>:<tag> --image <name>:<tag>

2. create a task to track image updates

task create -n <taskname>-r <registryName> -c /dev/null -t <name>:<tag>

Thanks, Stijn

[sajayantony]

The base image is tracked using the FROM clause in your Dockerfile. If the source image is now in an ACR then you should update the Dockerfile to point to that.

[Stijnc]

Understood. But that would only trigger an application image update and leave the base image untouched.

[SteveLasker]

I think what you’re asking is:

• If my vase image is in an ACR which triggers if you do a push to the referenced tag
• would an az acr import also trigger the base image update notifications.

Is that accurate?

[klingac]

Any update on this?

[roestzwiee]

Any updates on this?

I wonder if it is possible to execute the import on a schedule. Will it properly resolve updates?

[Racv]

Hi I have the same issue..

I got this node public image imported into my private ACR as node:16-alpine.. and all my app image are referencing this internal base image.

Now if new updates are coming in public node image in docker hub will my copy base image get updated in my private ACR automatically?

@SteveLasker