Failed to start container: unable to sethostname when calling #5829
Labels
area/kubelet
area/test
kind/bug
Categorizes issue or PR as related to a bug.
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
sig/node
Categorizes an issue or PR as relevant to SIG Node.
The e2e tests started failing sometime this afternoon because docker was not able to set the hostname.
Sample e2e run: go/k8healthz/job/kubernetes-e2e-gce/3797/consoleFull
The log is full of sethostname errors:
kubelet uses
pod.name
as the container hostname (I am not sure why). In the example above, the hostname is 83 characters, which has exceeded the max length of 64 on the system.The cause of this is that static pods (i.e., pods from file/http sources) use
podName-hostname
as the actual pod name so that we can distinguish pods from different nodes. #5775 replaced os.Hostname() with kubelet.Hostname. This led to the change of hostname frome2e-test-jenkins-minion-4gnu
toe2e-test-jenkins-minion-4gnu.c.kubernetes-jenkins.internal
, thus exceeding the limit.The text was updated successfully, but these errors were encountered: