Kubetail not display logs of main container when use initContainers

[EnziinSystem]

kubetail version : 1.6.11-SNAPSHOT

I use the initContainers check status MySQL service when it startup.

...
    spec:
      initContainers:
        - name: init-mysql
          image: busybox
          command: ['sh', '-c', "until nslookup mysql; do echo waiting for mysql; sleep 2; done;"]
      containers:
        - name: app-service
          image: app-service:1.0
...

Kubetail display logs from init containers, when the init containers are complete, it does not display logs of "app-service"

[app-service-6bfc85597c-nrbcm init-mysql] Server:		10.152.183.10 
[app-service-6bfc85597c-nrbcm init-mysql] Address:	10.152.183.10:53 
[app-service-6bfc85597c-nrbcm init-mysql]  
[app-service-6bfc85597c-nrbcm init-mysql] Name:	mysql.default.svc.cluster.local 
[app-service-6bfc85597c-nrbcm init-mysql] Address: 10.152.183.217 
[app-service-6bfc85597c-nrbcm init-mysql]  
[app-service-6bfc85597c-nrbcm init-mysql] *** Can't find mysql.svc.cluster.local: No answer 
[app-service-6bfc85597c-nrbcm init-mysql] *** Can't find mysql.cluster.local: No answer 
[app-service-6bfc85597c-nrbcm init-mysql] *** Can't find mysql.default.svc.cluster.local: No answer 
[app-service-6bfc85597c-nrbcm init-mysql] *** Can't find mysql.svc.cluster.local: No answer 
[app-service-6bfc85597c-nrbcm init-mysql] *** Can't find mysql.cluster.local: No answer 
[app-service-6bfc85597c-nrbcm init-mysql] 

Kube stops here, no logs while "app-service" still working.

[johanhaleby]

Never used init containers myself, but I would suspect that this has to do with kubetail not finding the other pods at the time it finds the init container. I think that solving #67 and #33 would also solve this issue.