I really didn't want to write a "hate" piece, but I've been backed into a corner... AT&T Uverse Internet DOES NOT WORK with Docker Hub. Also, AT&T wants ME TO PAY to have it fixed. Here's my story.
**UPDATE 9/25/2015**
Uverse is now working with Docker Hub. Thanks for everyone that was involved!
I had Uverse installed on 9/21/2015. I had been hacking on a new Docker Machine piece on my Verizon MiFi for a few days while I was at the office. Since my kitchen is being remodeled, I wanted to be there so I could monitor the progress. So, I'll just work from home. Today is 9/24/2015.
I finished a commit and needed to run a build. So I used my Docker Machine host to do that. I began the process and it got stuck:
kcoleman-mbp:machine kcoleman$ make script/validate-dco Congratulations! All commits are properly signed with the DCO! script/validate-gofmt Congratulations! All Go source files are properly formatted. script/test ./... Sending build context to Docker daemon 131.8 MB Step 0 : FROM golang:1.4.2-cross Pulling repository docker.io/library/golang Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/golang/images. You may want to check your internet connection or if you are behind a proxy. make: *** [test] Error 1
What? That's weird. Well what about just trying to run a container?
kcoleman-mbp:v050-dev kcoleman$ docker run -ti busybox Unable to find image 'busybox:latest' locally Pulling repository docker.io/library/busybox Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/busybox/images. You may want to check your internet connection or if you are behind a proxy.
Maybe it's an issue with my home network since I have another router. I hopped on the Uverse Wifi directly, same thing. Disabled the entire firewall, same thing. Gave my mac IP Passthrough, same thing.
Well that's not good. Lets hop over on my Verizon MiFi and do the same thing:
kcoleman-mbp:v050-dev kcoleman$ docker run -ti busybox Unable to find image 'busybox:latest' locally latest: Pulling from library/busybox cfa753dfea5e: Pull complete d7057cb02084: Pull complete library/busybox:latest: The image you are pulling has been verified. Important: image verification is a tech preview feature and should not be relied on to provide security. Digest: sha256:16a2a52884c2a9481ed267c2d46483eac7693b813a63132368ab098a71303f8a Status: Downloaded newer image for busybox:latest / #
Looks like we found our culprit. When I get on my MiFi, everything is working as normal. Time to call Support.
Immediately, I knew this wasn't going to go well. I talked to a nice lady and I asked to go ahead and escalate me. She sent me right to her manager. Unfortunately for Brian, he was in for a whirlwind of a time. I did my best to explain what Docker is and how the AT&T network is blocking access to it. He wanted to change the DNS servers. I obliged and changed my DNS servers and the same thing happened. Then he said, I'm sorry but we can't help you. WHAT? You can't help me? He said that I should try calling AT&T ConnecTech. What's AT&T ConnecTech? Well it's a service for people who don't know how to computer. For instance, they charge you $49.95 to help get your email client setup. I asked, "So in my case where it's going to take deep technical expertise, what am I looking at?" He said "$149.95". WHAT??!!?! AT&T WANTS ME TO PAY THEM $150 SO THEY CAN FIX A PROBLEM ON THEIR NETWORK FOR A PAYING CUSTOMER?? Brian refused to help me any further because this is out of their scope. He wouldn't even escalate me to another engineer.
I'm absolutely turned off by AT&T. This is dumb founding that they refuse to get me in touch with a representative that understands how to use just a tiny bit of advanced technology.
The sad part is, my wife loves Uverse
Look... I'm not alone!
Huh? #Docker pic.twitter.com/QAUcnwYl0I
— Sohel Almozaini (@i_Sohel) September 24, 2015
@rnelson0 @KendrickColeman Yeah, it seems that there's something wrong.
— Sohel Almozaini (@i_Sohel) September 24, 2015
Please share this so AT&T gets their act together. I have no idea how to make them aware of the issue unless it spreads.
**UPDATE 9/24/15 4:01pm EST**
Thanks to Rob Nelson (@rnelson0) for opening an internal ticket at AT&T. I have the SEP# if anyone needs it
**UPDATE 9/24/15 9:03pm EST**
Matthew, the product manager for Docker Hub has reached out and said that they are going to reach out to AT&T and see if there is anything that can be done from their end
**UPDATE 9/25/2015 10:50am**
Uverse is now working with Docker Hub. Thanks for everyone that was involved!
@i_Sohel @rnelson0 @Uverse yep. confirmed working for me again… whew. Updating blog article now. pic.twitter.com/J7qI5GUNYS
BTW, they need to learn how to use Twitter...
