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

build: cannot tar container entries: 0 errors occurred #9379

Closed
edsantiago opened this issue Feb 15, 2021 · 9 comments
Closed

build: cannot tar container entries: 0 errors occurred #9379

edsantiago opened this issue Feb 15, 2021 · 9 comments
Labels
flakes Flakes from Continuous Integration 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. remote Problem is in podman-remote stale-issue

Comments

@edsantiago
Copy link
Member

Another unfortunate flake that happens in multiple tests, so I can't easily analyze it:

Running: podman-remote [options] build --layers=true -t test --file /tmp/podman_test768134587/Dockerfile /tmp/podman_test768134587
time="2021-02-14T09:34:12-06:00" level=error msg="cannot tar container entries [/tmp/podman_test768134587/Dockerfile /tmp/podman_test768134587] error: 0 errors occurred:\n\t\n\n"
Error: 0 errors occurred:
...
Exit code is 125, expected 0 (or maybe the other way around, I can never understand ginkgo diagnostics)

This is happening all over the place, and is now our number-one flake. It is not easily characterized other than "podman-remote build". It seems to have started on February 8. I recommend treating this as very high priority due to the number of flakes yesterday.

Podman rmi [It] podman rmi with cached images

Podman rmi [It] podman image rm - concurrent with shared layers

Podman rmi [It] podman rmi -a with parent|child images

Podman prune [It] podman image prune skip cache images

@edsantiago edsantiago added flakes Flakes from Continuous Integration kind/bug Categorizes issue or PR as related to a bug. remote Problem is in podman-remote labels Feb 15, 2021
@vrothberg
Copy link
Member

vrothberg commented Feb 15, 2021

I think we may need @nalind's force.

@edsantiago
Copy link
Member Author

edsantiago commented Mar 1, 2021

Podman images [It] podman images --all flag

Podman run entrypoint [It] podman run entrypoint

@edsantiago
Copy link
Member Author

Can someone please make this a priority? It is now the number one flake.

Podman rmi [It] podman image rm - concurrent with shared layers

FWIW it seems to be correlated with the following error:

Error: 1 error occurred:
         	* error reading image "2a4cefc9e51e81ad10c4e9b67f99ec00be58b8a29bb900940bb322b56dca00c1" as image: error locating item named "manifest" for image with ID "2a4cefc9e51e81ad10c4e9b67f99ec00be58b8a29bb900940bb322b56dca00c1": file does not exist

@edsantiago
Copy link
Member Author

sys: build with copy-from referencing the base image

Podman rmi [It] podman image rm - concurrent with shared layers

Podman run entrypoint [It] podman run no command, entrypoint, or cmd

Podman images [It] podman images filter since image

Of possible interest: a lot of failures in one specific test run. That suggests that maybe something happens on a particular system, such that once this triggers, more tests will also fail with the same problem?

@edsantiago
Copy link
Member Author

sys: podman build - does not gobble stdin that does not belong to it

sys: podman build --layers test

@edsantiago
Copy link
Member Author

Please. Please please please please, someone fix this.

Podman rmi [It] podman rmi with cached images

Podman rmi [It] podman image rm - concurrent with shared layers

sys: podman build --layers test

sys: build with copy-from referencing the base image

@vrothberg
Copy link
Member

I bookmarked the issue and want to have a look at it this week. If others are faster, I would not complain :)

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@edsantiago
Copy link
Member Author

I haven't seen this one since #9717 merged. Thanks, @nalind!

@github-actions 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 Sep 22, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
flakes Flakes from Continuous Integration 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. remote Problem is in podman-remote stale-issue
Projects
None yet
Development

No branches or pull requests

2 participants