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

podman-remote: run --rm: Error removing container #7340

Closed
edsantiago opened this issue Aug 17, 2020 · 4 comments · Fixed by #7561
Closed

podman-remote: run --rm: Error removing container #7340

edsantiago opened this issue Aug 17, 2020 · 4 comments · Fixed by #7561
Assignees
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

Comments

@edsantiago
Copy link
Member

Another podman-remote flake, probably a race condition. I don't think this is the same as #7195 because when it happens I actually get output.

$ podman rm -a;podman volume rm -a
$ expect=$(./bin/podman-remote run --rm -v testvol1:/etc/apk alpine_labels ls /etc/apk)
$ while :;do got=$(./bin/podman-remote run --rm -v testvol1:/etc/apk alpine_labels ls /etc/apk); test "$got" = "$expect" || echo "got: $got";done
ERRO[0000] Error removing container 96e24969a069225db3cfdc27a724172fac29465ac911fa2974f68a94f3706b28: no container with name or ID 96e24969a069225db3cfdc27a724172fac29465ac911fa2974f68a94f3706b28 found: no such container
ERRO[0000] Error removing container e8834ac68b23e1720beed42e68b3e6de250629af7bd0295b9c9f62bf179c4912: container e8834ac68b23e1720beed42e68b3e6de250629af7bd0295b9c9f62bf179c4912 does not exist in database: no such container
ERRO[0000] Error removing container 3e4fcf50ba72d454ba81548dbfdff17d10a439001bb1a28a76f7165ede45eb4d: no container with name or ID 3e4fcf50ba72d454ba81548dbfdff17d10a439001bb1a28a76f7165ede45eb4d found: no such container
ERRO[0000] Error removing container 933bb8451d833c6c04399315edb91a8fa4900991f4f4f8f73c5cf0ac9e5f6ff9: container 933bb8451d833c6c04399315edb91a8fa4900991f4f4f8f73c5cf0ac9e5f6ff9 does not exist in database: no such container
^C

Note that there are two distinct error messages:

  • no container with name or ID ...
  • container ... does not exist in database

Exit status, FWIW, is 0 even with the error.

master @ 47108e2, root and rootless

I've seen it even without the -v testvol, but it reproduces much more quickly with -v. As in, less than five seconds to get an error message on my f32 laptop.

@edsantiago edsantiago added flakes Flakes from Continuous Integration remote Problem is in podman-remote labels Aug 17, 2020
@edsantiago
Copy link
Member Author

CI flakes in the field:

Podman run with volumes [It] podman named volume copyup

(The above might also show evidence of #7195. I haven't looked closely enough yet)

@vrothberg vrothberg self-assigned this Sep 8, 2020
@vrothberg
Copy link
Member

Looking into this now. Thanks a lot for providing all the details, @edsantiago !

@vrothberg
Copy link
Member

Looking at the remote code I found that --rm --detach is broken. Will prepare a fix for that as well.

@vrothberg
Copy link
Member

#7561 to fix both issues

@mheon mheon added the kind/bug Categorizes issue or PR as related to a bug. label Sep 9, 2020
vrothberg added a commit to vrothberg/libpod that referenced this issue Sep 11, 2020
As error types are not preserved on the client side (due to marshaling),
we cannot use `errors.Cause(...)` and friends but, unfortunately, have
to fall back to looking for substring the error messages.

Change the error checks in remote run to do substring matches and fix
issue containers#7340.

Fixes: containers#7340
Signed-off-by: Valentin Rothberg <[email protected]>
cevich added a commit to cevich/podman that referenced this issue Mar 4, 2021
This test frequently flakes on at least one platform during daily
cirrus-cron runs on the v2.2 branch.  Since this is not happening on
other versions, assume it's some kind of difficult-to-find/fix race
condition.  Skip the test on all platforms to cut down on noise.

Ref: containers#7340

Signed-off-by: Chris Evich <[email protected]>
@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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants