That's odd. Shouldn't be an issue with carriers, but rather some sort of firewall configuration.
I saw in a previous comment that you attempted to change the DNS for your Docker service, but weren't sure if you did it right. Well, here's how to do it, if you want to try it:
Edit the file "/etc/resolv.conf" and change the value of "nameserver" to 8.8.8.8. Save the file and restart the docker service with "sudo systemctl restart docker".
Can you curl the URL registry-1.docker.io/v2/, then? If not, I'm having a hard time believing it's not related to some network setting. Sorry I couldn't be of more help!
That's odd. Shouldn't be an issue with carriers, but rather some sort of firewall configuration.
I saw in a previous comment that you attempted to change the DNS for your Docker service, but weren't sure if you did it right. Well, here's how to do it, if you want to try it:
Edit the file "/etc/resolv.conf" and change the value of "nameserver" to 8.8.8.8. Save the file and restart the docker service with "sudo systemctl restart docker".
ok so here is my etc/resolv.conf
and it came back...
Can you curl the URL registry-1.docker.io/v2/, then? If not, I'm having a hard time believing it's not related to some network setting. Sorry I couldn't be of more help!
Yes I can it just say I'm unauthorized in a JSOn response