https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# general
a
This message was deleted.
m
BTW, docker version is as follows:
Copy code
$ docker version
Client: Docker Engine - Community
 Version:           19.03.13
 API version:       1.40
 Go version:        go1.13.15
 Git commit:        4484c46d9d
 Built:             Wed Sep 16 17:03:54 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.13
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       4484c46d9d
  Built:            Wed Sep 16 17:01:49 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.3
  GitCommit:        269548fa27e0089a8b8278fc4fc781d7f65a939b
 runc:
  Version:          1.0.0-rc92
  GitCommit:        ff819c7e9184c13b7c2607fe6c30ae19403a7aff
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683
I’m also seeing 
Could not resolve host: <http://git.rancher.io|git.rancher.io>
in the rancher/server logs
Copy code
kubectl run -it --rm --restart=Never busybox --image=busybox:1.28 -- nslookup <http://www.google.com|www.google.com>
If you don't see a command prompt, try pressing enter.
nslookup: can't resolve '<http://www.google.com|www.google.com>'
pod "busybox" deleted
pod default/busybox terminated (Error)
I’ve addressed some firewall issues, but I’m still having problems with network connectivity. If I do an 
nslookup
from a 
busybox
container in docker it works, but as a rancher pod not so much
Copy code
$ docker run -it busybox:1.28 nslookup <http://www.google.com|www.google.com>
Server:    192.168.17.178
Address 1: 192.168.17.178 <http://legolas.inhouse-broker.org|legolas.inhouse-broker.org>

Name:      <http://www.google.com|www.google.com>
Address 1: 2607:f8b0:4009:807::2004 <http://ord38s19-in-x04.1e100.net|ord38s19-in-x04.1e100.net>
Address 2: 172.217.5.4 <http://lga15s49-in-f4.1e100.net|lga15s49-in-f4.1e100.net>
with 
kubectl
no good
Copy code
$ kubectl run -it --rm --restart=Never busybox --image=busybox:1.28 -- nslookup <http://www.google.com|www.google.com>
If you don't see a command prompt, try pressing enter.
nslookup: can't resolve '<http://www.google.com|www.google.com>'
pod "busybox" deleted
pod default/busybox terminated (Error)
h
only thing I can think of is double check your entries in hosts file and resolv.conf (on the host). then restart network and docker service
m
There really isn’t much in the host file, but I am seeing this…
Copy code
$ kubectl -n kube-system get pods -l k8s-app=kube-dns
NAME                       READY   STATUS             RESTARTS   AGE
coredns-685d6d555d-l4v4d   0/1     CrashLoopBackOff   205        10h
Copy code
$ cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
when I do a
Copy code
kubectl -n kube-system describe pod coredns-685d6d555d-l4v4d
I see there is a potential cgroup problem
Copy code
Warning  Failed          74m (x4 over 75m)      kubelet  Error: failed to start container "coredns": Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:326: applying cgroup configuration for process caused: failed to write 1 to memory.kmem.limit_in_bytes: write /sys/fs/cgroup/memory/kubepods/burstable/podc57e2d18-9421-4c84-8d9b-f97dcd3ee3f2/coredns/memory.kmem.limit_in_bytes: operation not supported: unknown
but that seems like it is just a warning and not fatal
164 Views
Open in Slack
PreviousNext
Powered by