On Fri, 29 Sep 2023 16:17:47 -0400, Chuck Payne wrote:


> Do the following
>
> docker ps
>
> get the hash for the container, or look in the logs for the hash, then
> do the following
>
> docker logs --follow <hashid or if you are name for the docker, then use
> docker name>
>
> This will give you all the out of the docker container since you started
> to run it .

Thanks, Chuck - unfortunately, the issue happens before the container
image is even pulled down.  Rootless docker uses a userspace network layer
that seems to interfere in some (but not all instances) with even pulling
the image to start with.

We're looking at network configuration inside that userspace stuff using
the 'nsenter' command to look at a tap interface that sits between the
rootless docker daemon and the outside world.

--
 Jim Henderson
 Please keep on-topic replies on the list so everyone benefits