-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Onbuild triggers not cleared for downstream (grandchild) images #1308
Comments
FYI onbuild is deprecated |
I'm a bit confused by that link. It looks to me like the There also seems to be some work from earlier this year (after that deprecation issue was closed) on enhancing the |
I've seen some other comments that it was heading that way |
From this comment #816 (comment) it looks like its still supported. |
Thanks for the quick fix! |
Hi, we make heavy usage of
ONBUILD
instructions and base images to standardize our projects. We have found that when using the buildkit and building images from base images that specifyONBUILD
instructions those triggers are not being cleared for grandchild images. It can be observed through both behavior and the json metadata returned fromdocker inpsect
To reproduce:
Base image
foo-base
withDockerfile
:Child image
foo-child
withDockerfile
:Grandchild image
foo-grandchild
withDockerfile
:When built with the buildkit,
foo-child
image'sdocker inspect
returns:When built without the buildkit the
foo-child
image'sdocker inspect
returns:The
ContainerConfig.OnBuild
values differ between the two of these.When building
foo-grandchild
fromfoo-child
built with the buildkit you get the following output:When building
foo-grandchild
fromfoo-child
built without the buildkit you get the following output:Is this behavior intended? The divergence in behavior between the old builder and the buildkit is causing some of our builds to fail. If you need any additional information please let me know.
The text was updated successfully, but these errors were encountered: