No more automatic rebuilds on upstream images pushes?

[tyranron]

With recent Docker Hub update it seems that there is no way anymore to automatically rebuild images when another image is pushed.

In previous Docker Hub design this setting was on the Build Settings tab after the Build Rulessection and before the Build Triggers section. It was accepting Docker Hub repository names (like alpine, php, rustlang/rust, etc). If some of specified repos pushed tags the build automatically triggered for the current repo. This was a huge help for maintaining image, as allowed cascade rebuilds to keep images up-to-date.

Currently, there is no such section anymore in build settings:

It's highly desirable to return those feature, or provide a reasonable alternative. 🙏🙏🙏

[mark-stopka]

Any reaction on this from Docker? I think it was widely used functionality...

[mitar]

I agree. I sent them a support e-mail but didn't get any response. It seems to me that old images are still supporting this and are being rebuild when a parent image is pushed, but there is nowhere in UI to configure/see this.

This is for us the main reason we are using Docker Hub over other solutions. I am glad about the UI update, but this feature is critical for us.

[frol]

I have also sent an e-mail to hub-feedback@docker.com a few days ago and no response since then.

[mitar]

Has anyone got any response? The funny thing is that we are paying for Docker Hub mostly because of this feature.

I was even thinking that this could be done as a simple 3rd party service where you would register your image and configure it so that Docker Hub POSTs there every time image is build. And then you could also register other images to be triggered when the original image is rebuilt.

[frol]

@mitar I have not received any response from Docker Hub team what so ever even after they silently dropped my 10M+ image (#1741).

[mitar]

Yes, I have seen that issue. :-( Not fun.

[stayallive]

It seems there is an old build system (hubbuild) and a new one that is enabled for new images since a few of my newer have the repository links but older don't.

However it looks like you can switch over. It will keep your "old" build settings active too... so you might want to disable them.

Go to: https://cloud.docker.com/repository/docker/<accountname>/<respository>/builds

^ change out accountname & repository for your own and use the button in the top right to configure automated builds. When that's setup you can enable repository links.

Not sure what the actual deal is... but this works for me :)

[mitar]

Interesting. So what I see is that for old images links still exist and get triggered, I just do not see them/are able to configure them.

But this is new. When they released this there was no such option. Now I see that for the new image I created after the release, under "configure automatic builds" there is an option "repository links" and I can enable image to be rebuild when FROM image gets pushed. So it is not possible to configure anymore custom links, but just FROM. For me, this is good enough.

In tooltip there is a comment though: "Only works for non-official images." So if my image uses official image in FROM I cannot make it re-build when official image changes?

[lshep]

I'm finding that even with the REPOSITORY LINKS Enable for Base image still does not work. I have two repositories and one image is built from the other bioconductor/devel_base2 and bioconductor/devel_core2. I have a FROM bioconductor/devel_base2 in the Dockerfile of bioconductor/devel_core2 and the enable from Base image is selected and saved; but when I rebuild devel_base2 either interactively or a manual trigger - a new build of devel_core2 is not triggered. Please bring this feature back! I feel like it had to have been highly used.
I really would need the feature of only being autobuilt on an update to the upstream image and not on pushes to the branch and whatnot.

[tonglil]

This hasn't been working for the last 2 weeks for repos I have that depend on https://hub.docker.com/r/google/cloud-sdk/

[ruffsl]

I've also seen this feature suddenly stop working. From my logs, it was working about a month ago.

[znmeb]

I just discovered this today - my images haven't been rebuilt in three months, so it broke some time in June :-(

I just looked at the settings - it was set to automatically rebuild if the base image changed. But apparently there's a new piece of fine print - it only works for non-official base images. All my base images are official, like Postgres and pgAdmin4.

[Edzilla2000]

I just discovered this today - my images haven't been rebuilt in three months, so it broke some time in June :-(

I just looked at the settings - it was set to automatically rebuild if the base image changed. But apparently there's a new piece of fine print - it only works for non-official base images. All my base images are official, like Postgres and pgAdmin4.

I have the same issue, I use an official base image and my image isn't rebuild anymore :s

[Al2Klimov]

All of you – complain.

I – just fixed it by myself: https://hub.docker.com/r/grandmaster/dockerhub-chainreactor

😎

[github-actions]

We are clearing up our old issues and your ticket has been open for one year with no activity. Remove stale label or comment or this will be closed in 15 days.

[ruffsl]

Let's keep this ticket open while we wait for an official response...

[github-actions]

We are clearing up our old issues and your ticket has been open for 6 months with no activity. Remove stale label or comment or this will be closed in 15 days.

[ddriddle]

Any chance this will ever be fixed?

[fsacer]

I also think that from a security perspective this is a much-needed feature, hopefully, we can get it back in 2022?

[abunch]

Maybe 2023 is the year they'll get Repository Links working again...or maybe they should remove the option from the interface and stop misleading folks.

[janhoy]

How about 2024? 🤣