Lab15_1 step 16 ubuntu pod, Is the package apt-transport-https installed?

sylvainmartin

in Step 16,
``kubectl run -i --tty ubuntu \
--image=ubuntu:16.04 --restart=Never -- bash -il

Looks like the repos use https and since the container do not contain apt-transport-https, it will not update.
curl or wget is not on the image so I don't see a way to even fetch the package to add it. Any advice?

Output:
root@ubuntu:/etc/apt# apt update
Reading package lists... Done
E: The method driver /usr/lib/apt/methods/https could not be found.
N: Is the package apt-transport-https installed?
E: The method driver /usr/lib/apt/methods/https could not be found.
N: Is the package apt-transport-https installed?
E: The method driver /usr/lib/apt/methods/https could not be found.
N: Is the package apt-transport-https installed?
E: The method driver /usr/lib/apt/methods/https could not be found.
N: Is the package apt-transport-https installed?

chrispokorni

Hi @sylvainmartin,
In this lab the only strange thing I experience is that I can no longer (at least for now) download the helm 2.7 package. I downloaded helm 2.8 instead to be able to reproduce step 16, and with both images "ubuntu:16.04" and just plain "ubuntu" I was able to "apt (and apt-get) update/upgrade/install". I would expect we both pulled the same ubuntu:16.04 image from the repo.
Did you try re-creating the client pod? Did you see the same behavior?
Regards,
-Chris

sylvainmartin

after much conntrack'ing, tcpdump'ing I found my issue... it's appending my search extra from my k8s dhcp vlan to /etc/resolv.conf and I have a *.mydomain.com dns entry that points to my treaffik frontend for my docker env

10:23:35.963407 IP 10.7.0.155.52089 > google-public-dns-a.google.com.domain: 7258+ A? security.ubuntu.com.svc.cluster.local. (55)
10:23:35.968852 IP 10.7.0.155.39434 > google-public-dns-a.google.com.domain: 63880+ A? archive.ubuntu.com.svc.cluster.local. (54)
10:23:35.998476 IP 10.7.0.155.61300 > google-public-dns-a.google.com.domain: 12404+ A? security.ubuntu.com.cluster.local. (51)
10:23:35.998687 IP 10.7.0.155.61300 > google-public-dns-a.google.com.domain: 42805+ AAAA? security.ubuntu.com.cluster.local. (51)
10:23:36.040027 IP 10.7.0.155.33428 > google-public-dns-a.google.com.domain: 17361+ A? security.ubuntu.com.vlan1007.mydomain.com. (58)
10:23:36.040277 IP 10.7.0.155.33428 > google-public-dns-a.google.com.domain: 4984+ AAAA? security.ubuntu.com.vlan1007.mydomain.com. (58)

root@ubuntu:/# cat /etc/resolv.conf 
nameserver 10.96.0.10
search default.svc.cluster.local svc.cluster.local cluster.local vlan1007.mydomain.com int.mydomain.com mydomain.com
options ndots:5
 
root@ubuntu:/# cat > /etc/resolv.conf
nameserver 10.96.0.10
options ndots:5

root@ubuntu:/# apt update
Get:1 http://archive.ubuntu.com/ubuntu xenial InRelease [247 kB]

chrispokorni

Ah, the fun of dealing with DNS
I assume in Lab 10.1 (Ingress) step 15 you did not encounter any issues while running "apt update" and "apt install".

sylvainmartin

I skipped over that one, I'm going to redo all of them again, I've got my test next week. but I figured since part of the test will most likely have a "this is broken, fix it" I might has well try to figure out the problem

chrispokorni

Nice troubleshooting!
Good luck on your test!