podman: [intermittent]: podman run -a stdin&stderr: read unixpacket: connection reset by peer

This is a combination that I can find no realistic use for, but even so I think merits attention because it might present itself in other more real-world situations:

# echo true | podman run -a stdin -a stderr --tty=false alpine sh
Error: error attaching to container 22e7b45a00508b0e60a27288bb6c745100a2ee42335800de1d8e246cfe24bd48: read unixpacket @->/var/run/libpod/socket/22e7b45a00508b0e60a27288bb6c745100a2ee42335800de1d8e246cfe24bd48/attach: read: connection reset by peer

Reproduces maybe one in five attempts; the rest of the time it succeeds. It also fails with echo ls / and echo ls /sdf, but does not (seem to) fail with </dev/null (redirection, not pipe).

--log-level=debug adds nothing of value AFAICT—both pass and fail look identical to my eye—but I will provide on request.

podman-1.4.0-2.fc29 and fc30; but I think I’ve seen it before, just never taken time to pursue it. I can look in logs if necessary.