You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dockerfile-based builds tools (kaniko [1], buildah [2]) support two kinds of inputs:
Build context - this is typically source code or artifacts, and reside in the build context. These files are either COPYed or ADDed, and as a result a layer is added to the final image.
Volumes - these are often things like caches (image layers, npm, maven, etc). These are bind-mounted into the build container and do not directly result in layers being added to the final image. This can also be used to bind mount sensitive information that should not be present in a distributed image (ex - certificate authorities for private registries).
We should support volumes as a separate input for Build/BiuldRun objects, and provide a means for BuildStrategy authors to consume these volume mounts within the build process.
Dockerfile
-based builds tools (kaniko [1], buildah [2]) support two kinds of inputs:COPY
ed orADD
ed, and as a result a layer is added to the final image.We should support
volumes
as a separate input forBuild
/BiuldRun
objects, and provide a means forBuildStrategy
authors to consume these volume mounts within the build process.[1] https://github.com/GoogleContainerTools/kaniko#caching
[2] https://github.com/containers/buildah/blob/master/docs/buildah-mount.md
The text was updated successfully, but these errors were encountered: