This repository has been archived by the owner on Jun 18, 2020. It is now read-only.
As a pack user, I only see a single copy of the generated image SHAs #45
Comments
ekcasey
added a commit
to buildpacks/lifecycle
that referenced
this issue
Mar 26, 2019
* temporarily set output destination for standard logger to discard before writing a remote image * surpresses ggcr output [buildpacks/roadmap#45]
ekcasey
added a commit
to buildpacks/lifecycle
that referenced
this issue
Mar 27, 2019
* temporarily set output destination for standard logger to discard before writing a remote image * surpresses ggcr output [buildpacks/roadmap#45] Signed-off-by: Emily Casey <[email protected]>
ekcasey
added a commit
to buildpacks/lifecycle
that referenced
this issue
Mar 28, 2019
* NOTE: we are silencing the standard logger * all lifecycle phases must create and use their own logger [buildpacks/roadmap#45] Signed-off-by: Emily Casey <[email protected]> Signed-off-by: Danny Joyce <[email protected]>
|
Not seeing SHAs generated from go-containerregistry when I run pack build, accepting. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Remove "wall of SHAs" coming from ggcr (but keep exporter SHAs).
Acceptance Criteria
When I build an OCI image with
pack buildand any combination of valid optionsThen I don't see any SHAs that originate from the go-containerregistry
And I see the SHAs intentionally output by the exporter
The text was updated successfully, but these errors were encountered: