Chapter 7 - Please Help about devops_for_the_desperate

[bradleyd]

Hey @jasencarroll, I am trying to understand what you have going on here. There is a lot of output and you changing stuff. I think you have two versions of docker running? There should only be one version of docker and that is inside minikube. Make sure you are setting the minikube docker env in the shell you are working in. Also, you should only installed the docker client locally.

I hope that helps and gets digging around more.

[jasencarroll]

I know I posted a lot and I just wanted to say I really do appreciate this book and it's content, I'm learning a ton.

[jasencarroll]

@bradleyd, thanks for the response; I get that it was a lot to read through. When I only had one docker version, which was inside of minikube, I would consistently see this output.

Unable to resolve the current Docker CLI context "default": context "default" does not exist.

Have you run into that before? Does it matter to me?

---

At some point, I installed Docker Desktop and progressed through this chapter though that couldn't be replicated on any other machines, and I don't count that as success.

---

From the example above, I could not get the Status to change. Based on your message, I should have the Docker binaries installed locally; this would be in the appropriate /bin/ in my path since I'm in Ubuntu. I should not install the Docker binaries inside of minikube. minikube should be fine as is, and once the binaries are in my bin, I can tell minikube to grab that env and activate.

jasen@Renegade:telnet-server(main*)$ minikube kubectl -- get pods -l app=telnet-server
NAME                             READY   STATUS             RESTARTS   AGE
telnet-server-5fd648cdd9-2rljq   0/1     ImagePullBackOff   0          10m
telnet-server-5fd648cdd9-v8j7f   0/1     ImagePullBackOff   0          10m
telnet-server-68f9f68c45-ggwnl   0/1     ImagePullBackOff   0          9m58s

Please confirm/deny if my statements are factual so far.

---

By this point, I realized docked had crashed. I don't understand why, and trying to rerun it resulted in this weird stuff:

jasen@Renegade:Downloads$ sudo dockerd &
[2] 21226

[2]+  Stopped                 sudo dockerd
jasen@Renegade:Downloads$ sudo dockerd &

---

I was running sudo dockerd & to suppress the Unable to resolve the current Docker CLI context "default": context "default" does not exist but maybe that's where I'm confused and doing the wrong thing. Should minikube be running sudo docker & as part of its automation and I should be working about this?

Any insight would be greatly appreciated before I attempt again. :)

[bradleyd]

Sorry nothings coming to mind; I have never seen that error following the chapters. You have minikube, virtualbox installed? Did you deviate from the book at all? I can try doing that on Ubuntu and see what happens.

[jasencarroll]

@bradleyd, thanks for reviewing and letting me know. Don't do anything yet, I'd hate to waste your time. I will advise when I get back to this with a fresh environment. I suppose I could try this second half of the book on Windows too since Vagrant was the limitation earlier.

[bradleyd]

Any updates before I close this ticket?