Failed to get pidID : unable to find pod main pid

[debianmaster]

on 3.11 alpha pod-network controller is throwing this error. when a work load is deployed

time="2018-10-10T10:09:41Z" level=info msg="Go Version: go1.9.4"
--
  | time="2018-10-10T10:09:41Z" level=info msg="Go OS/Arch: linux/amd64"
  | time="2018-10-10T10:09:41Z" level=info msg="operator-sdk Version: 0.0.5+git"
  | time="2018-10-10T10:09:41Z" level=info msg="Managing Pods Running on Node: ns536048"
  | time="2018-10-10T10:10:55Z" level=error msg="Failed to get pidID : unable to find pod main pid"
  | time="2018-10-10T10:10:55Z" level=error msg="Failed to process pod : unable to find pod main pid"
  | time="2018-10-10T10:10:55Z" level=error msg="error syncing key (test/test-1-5zvts): unable to find pod main pid"
  | time="2018-10-10T10:10:55Z" level=error msg="Failed to get pidID : unable to find pod main pid"
  | time="2018-10-10T10:10:55Z" level=error msg="Failed to process pod : unable to find pod main pid"
  | time="2018-10-10T10:10:55Z" level=error msg="error syncing key (test/test-1-5zvts): unable to find pod main pid"
  | time="2018-10-10T10:10:55Z" level=error msg="Failed to get pidID : unable to find pod main pid"
  | time="2018-10-10T10:10:55Z" level=error msg="Failed to process pod : unable to find pod main pid"
  | time="2018-10-10T10:10:55Z" level=error msg="error syncing key (test/test-1-5zvts): unable to find pod main pid"
  | time="2018-10-10T10:10:55Z" level=error msg="Failed to get pidID : unable to find pod main pid"
  | time="2018-10-10T10:10:55Z" level=error msg="Failed to process pod : unable to find pod main pid"
  | time="2018-10-10T10:10:55Z" level=error msg="error syncing key (test/test-1-5zvts): unable to find pod main pid"
  | time="2018-10-10T10:10:56Z" level=error msg="Failed to get pidID : unable to find pod main pid"
  | time="2018-10-10T10:10:56Z" level=error msg="Failed to process pod : unable to find pod main pid"
  | time="2018-10-10T10:10:56Z" level=error msg="error syncing key (test/test-1-5zvts): unable to find pod main pid"
  | time="2018-10-10T10:10:56Z" level=error msg="Failed to get pidID : unable to find pod main pid"
  | time="2018-10-10T10:10:56Z" level=error msg="Failed to process pod : unable to find pod main pid"
  | time="2018-10-10T10:10:56Z" level=error msg="error syncing key (test/test-1-5zvts): unable to find pod main pid"
  | time="2018-10-10T10:10:56Z" level=error msg="Failed to get pidID : unable to find pod main pid"
  | time="2018-10-10T10:10:56Z" level=error msg="Failed to process pod : unable to find pod main pid"
  | time="2018-10-10T10:10:56Z" level=error msg="error syncing key (test/test-1-5zvts): unable to find pod main pid"
  | time="2018-10-10T10:10:57Z" level=info msg="Pod test-1-5zvts previously initialized, ignoring"
  | time="2018-10-10T10:11:02Z" level=info msg="Pod test-1-5zvts previously initialized, ignoring"

[jaredallard]

Looks like this is caused by any container with more than one container running

istio-pod-network-controller/pkg/handler/handler.go

Lines 147 to 157 in 2260deb

	if len(containers) == 1 {
	inspect, err := h.dockerClient.ContainerInspect(dockerCtx, containers[0].ID)
	if err != nil {
	log.Error(err)
	return "", err
	}
	log.Debugf("Pod Namespace: %s - Pod Name: %s - Container PID: %d", podName, podNamespace, inspect.State.Pid)
	return fmt.Sprintf("%d", inspect.State.Pid), nil
	}