Skip to content
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

local.NewImage fails because docker.SaveImage returns multiple manifests. #63

Closed
ekcasey opened this issue Oct 5, 2020 · 0 comments · Fixed by #81
Closed

local.NewImage fails because docker.SaveImage returns multiple manifests. #63

ekcasey opened this issue Oct 5, 2020 · 0 comments · Fixed by #81
Labels
type/bug Something isn't working

Comments

@ekcasey
Copy link
Member

ekcasey commented Oct 5, 2020

Periodically when executing the lifecycle against the daemon errors like this occur:

ERROR: rebase working image: manifest.json had unexpected number of entries: 2

This happens when we are saving an image from the docker daemon to disk and we unexpectedly get more than one manifest.

imgutil/local/local.go

Lines 542 to 544 in afd98bd

if len(manifest) != 1 {
return nil, fmt.Errorf("manifest.json had unexpected number of entries: %d", len(manifest))
}

We should figure out how we get into this state and determine a mitigation.

@ekcasey ekcasey added the type/bug Something isn't working label Oct 5, 2020
ekcasey added a commit to buildpacks/lifecycle that referenced this issue Dec 10, 2020
Falls back to slower behavior if the daemon does not accept empty layers. This allows the lifecycle to be compatible with podman which requires all layers to be preset during a docker load. buildpacks/imgutil#80

Fixes "manifest.json had unexpected number of entries"  errors in analyze, export, and rebase resulting from a bug in our daemon save logic buildpacks/imgutil#63

Signed-off-by: Emily Casey <ecasey@vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant