Created attachment 1606077[details]
podman --log-level=debug run --rm alpine true
Command hangs for as long as I'm willing to wait (many minutes). ^C results in:
$ podman run --rm alpine true
^C
ERRO[0041] Error forwarding signal 2 to container d8223a16ec0a64015d1ebaae0a624cbe833d3b4f3c90d253e22d4dbfed2e62ed: container has already been removed
ERRO[0041] Error forwarding signal 15 to container d8223a16ec0a64015d1ebaae0a624cbe833d3b4f3c90d253e22d4dbfed2e62ed: container has already been removed
This is only with --rm. Plain 'podman run alpine true' exits 0 as expected.
podman-1.4.2-2.module+el8.1.0+3888+8b36fd52.x86_64
Comment 1Giuseppe Scrivano
2019-08-20 15:25:28 UTC
it seems to be caused by an old conmon. We'll need to upgrade the conmon package.
Test with podman-1.4.2-5.module+el8.1.0+4240+893c1ab8.x86_64 given steps with and the command can finished as expect, so set this to verified.
Details:
$ time podman run --rm alpine true
real 0m0.655s
user 0m0.130s
sys 0m0.131s
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2019:3403
Created attachment 1606077 [details] podman --log-level=debug run --rm alpine true Command hangs for as long as I'm willing to wait (many minutes). ^C results in: $ podman run --rm alpine true ^C ERRO[0041] Error forwarding signal 2 to container d8223a16ec0a64015d1ebaae0a624cbe833d3b4f3c90d253e22d4dbfed2e62ed: container has already been removed ERRO[0041] Error forwarding signal 15 to container d8223a16ec0a64015d1ebaae0a624cbe833d3b4f3c90d253e22d4dbfed2e62ed: container has already been removed This is only with --rm. Plain 'podman run alpine true' exits 0 as expected. podman-1.4.2-2.module+el8.1.0+3888+8b36fd52.x86_64