nc: bad address "docker container" · Issue #54 · docker ...
github.com › docker-library › busyboxNov 05, 2018 · So it seems to me that the Docker Hub scan date changed the "last updated" date for that image. I'll see if someone at docker can look as to why that happened (but it is unrelated to this issue). it was probably the server that pushes manifest lists getting an bad response and pushing an manifest identical to the already pushed manifest (which is why it has the same sha).
Version nginx:1.19.7-alpine, DNS issue ‘bad address’ · Issue ...
github.com › nginxinc › docker-nginxMar 19, 2013 · $ sudo docker run -ti --rm nginx:1.19-alpine ping -c 1 google.com ping: bad address 'google.com' $ sudo docker run -ti --rm alpine:3.13 ping -c 1 google.com ping: bad address 'google.com' $ sudo docker run -ti --rm alpine:3.12 ping -c 1 google.com PING google.com (216.58.201.142): 56 data bytes 64 bytes from 216.58.201.142: seq=0 ttl=61 time=16.582 ms --- google.com ping statistics --- 1 ...