8000 "EXTEND" to mark "non-instantiating" extension that doesnt run "ONBUILD" · Issue #11917 · moby/moby · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
"EXTEND" to mark "non-instantiating" extension that doesnt run "ONBUILD" #11917
Closed
@shaunc

Description

@shaunc

I have a base image nodebase for node apps which has

ONBUILD ADD package.json /tmp/package.json
ONBUILD RUN cd /tmp && npm install
ONBUILD RUN mkdir -p /app && cp -a /tmp/node_modules /app

I'd like to define an extension of it that includes postgres tools in the image. However, I don't want to have the "ONBUILDS" triggered in the extension -- rather they should be triggered in the "final" build with the app.

It would be nice to have

EXTEND nodebase

as a variant of from which supresses the "ONBUILD"s -- another Dockerfile built FROM the extension would then trigger them.

I see there are various proposals for "ONBUILD" floating around. Perhaps EXTEND would be a good place to control the staging of ONBUILDs, so that FROM could be kept simple.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0