podman run localhost/myapp:5c80fa645641 tries to pull: 'pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused': an image ID is not a tag
Run the image by bare ID (podman run 5c80fa645641 ...) or by a real tag (localhost/myapp:latest), not by repository plus ID. podman images lists REPOSITORY localhost/myapp TAG latest IMAGE ID 5c80fa645641. Writing localhost/myapp:5c80fa645641 asks for a tag named 5c80fa645641, which doesn't exist locally. Podman then treats localhost as a registry host and tries to pull over HTTPS: Trying to pull localhost/myapp:5c80fa645641... followed by three Failed, retrying in 1s ... pinging container registry localhost warnings and an error.
With podman run -d --name runner ... it is easy to miss. Nothing starts, and the next command (podman logs runner) says Error: no container with name or ID "runner" found: no such container, which looks like the container crashed.
To pin a specific build (for example to compare an older image with a rebuild), give it a tag: podman tag 5c80fa645641 localhost/myapp:v3, then podman run localhost/myapp:v3. Docker behaves the same way, because name:tag syntax never accepts an image ID as the tag.