-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
weird: FROM scratch + label + manifest = Error: choosing image instance: no image found in manifest list for architecture amd64, variant "", OS linux #19860
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
Another way to hose $ podman manifest create m
$ printf "FROM scratch\nARG TARGETARCH\n" | podman build -t i -f - |
Using |
edsantiago
added a commit
to edsantiago/libpod
that referenced
this issue
Sep 5, 2023
Primarily, build test images FROM scratch, not alpine, to avoid image pulls and network flakes and potential pull- the-rug-out errors if the base alpine image changes. This was much more complicated than it should've been, because creating unique arch-specific FROM-scratch images triggered a weird manifest bug, filed as containers#19860. Also: - add a teardown() to clean up manifests - remove test for skopeo (skopeo is required for sys tests) - remove unnecessary intermediate tmpdir - deduplicate, by looping over amd+arm - fix indentation - and, finally, clean up dangling images (this was the initial reason behind my diving in here. Such a simple thing, I thought.) Signed-off-by: Ed Santiago <santiago@redhat.com>
@flouthoc PTAL |
flouthoc
added a commit
to flouthoc/buildah
that referenced
this issue
Sep 7, 2023
A build case where base is `scratch` and only a `label` is added then no layer is created, its like tagging empty image, in such cases create a layer. Closes: containers/podman#19860 Signed-off-by: Aditya R <arajan@redhat.com>
PR containers/buildah#5031 should close this |
flouthoc
added a commit
to flouthoc/common
that referenced
this issue
Sep 13, 2023
Layer tree expectes to form a relation between child and parent instances, however it expects an instance from manifest list which is empty, following expectation is not possible and will always resuilt in error. Closes: containers/podman#19860 [NO NEW TESTS NEEDED] Image without layer cant be built in libimage, and `podman save` automatically malforms such image so no such external image can be loaded. Signed-off-by: Aditya R <arajan@redhat.com>
flouthoc
added a commit
to flouthoc/common
that referenced
this issue
Sep 14, 2023
Layer tree expectes to form a relation between child and parent instances, however it expects an instance from manifest list which is empty, following expectation is not possible and will always resuilt in error. Closes: containers/podman#19860 [NO NEW TESTS NEEDED] Image without layer cant be built in libimage, and `podman save` automatically malforms such image so no such external image can be loaded. Signed-off-by: Aditya R <arajan@redhat.com>
flouthoc
added a commit
to flouthoc/common
that referenced
this issue
Sep 14, 2023
Layer tree expectes to form a relation between child and parent instances, however it expects an instance from manifest list which is empty, following expectation is not possible and will always resuilt in error. Closes: containers/podman#19860 [NO NEW TESTS NEEDED] Image without layer cant be built in libimage, and `podman save` automatically malforms such image so no such external image can be loaded. Signed-off-by: Aditya R <arajan@redhat.com>
flouthoc
added a commit
to flouthoc/common
that referenced
this issue
Sep 14, 2023
Layer tree expectes to form a relation between child and parent instances, however it expects an instance from manifest list which is empty, following expectation is not possible and will always resuilt in error. Closes: containers/podman#19860 [NO NEW TESTS NEEDED] Image without layer cant be built in libimage, and `podman save` automatically malforms such image so no such external image can be loaded. Signed-off-by: Aditya R <arajan@redhat.com>
flouthoc
added a commit
to flouthoc/common
that referenced
this issue
Sep 18, 2023
Layer tree expectes to form a relation between child and parent instances, however it expects an instance from manifest list which is empty, following expectation is not possible and will always resuilt in error. Closes: containers/podman#19860 [NO NEW TESTS NEEDED] Image without layer cant be built in libimage, and `podman save` automatically malforms such image so no such external image can be loaded. Signed-off-by: Aditya R <arajan@redhat.com>
flouthoc
added a commit
to flouthoc/common
that referenced
this issue
Sep 18, 2023
Layer tree expectes to form a relation between child and parent instances, however it expects an instance from manifest list which is empty, following expectation is not possible and will always resuilt in error. Closes: containers/podman#19860 [NO NEW TESTS NEEDED] Image without layer cant be built in libimage, and `podman save` automatically malforms such image so no such external image can be loaded. Signed-off-by: Aditya R <arajan@redhat.com>
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Dec 19, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
No surprises. Nothing unusual. Now build a scratch image with a label, any label:
It can be done in either order (build first, then manifest create).
Removing the image succeeds (exit status 0, and image is successfully deleted) but with scary warnings:
The obvious fix is to add
build --platform=linux/amd64
-- nope, no difference.Removing
--label
fixes everything.The text was updated successfully, but these errors were encountered: