Interesting day - what to do if docker registry fails with timeout.

So today was interestingly frustating...

I've setup my Mac in order to use brew for mostly everything because I like installing stuff from terminal. ( Definetly this is a personal issue from the days I had to install and reinstall my Windows machine ).

Now I did my development setup to support a backend oriented programmer because that's what I do in my professional life. With this in mind I wanted to dive into writing a lambda in node because I will use that know how for work.

So after a few "brew installs" which went ahead without a hitch I started :

- sam init

- sam build

- sam local invoke ScheduledEventLogger --event events/event-cloudwatch-event.json

Yes, I used the setup sam can create for you - I did say I was testing stuff out.

And then this happened : "docker: Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 10.0.2.3:53: read udp 10.0.2.15:50524->10.0.2.3:53: i/o timeout."

Of course at this stage I popped up google search and start reading stackoverflow... So I tried a bunch of the things that were suggested - not a happy result in sight was to be seen. So then I've given up and said to myself that I need to get on the "tried and true" solution: uninstall and reinstall - but happiness was not in sight. And then I got onto : https://forums.docker.com/t/pulling-docker-images-i-o-timeout/740/6

So turned off and on my Wifi and "voila"

Still here - still coding

There is a question which HR loves to ask when interviewing a candidate : " Where do you see yourself in 5 years?" My answer: " I want to do this stuff even at 80... so the best things are in between" Not always loving HR but seeing the faces when they hear the answer makes me giggle. Also staying sane enough to be doing this job is a job of its own. Not losing your mind when every year there is a manager that wants a fully featured task in 2 weeks even if the whole team estimated it at 2 months, is again a job of its own. Not to mention the rate at which new stuff appears that may or may not be good in the long run - but one still has to learn it 'cause you never know.