"ERROR: failed to create cluster: failed to pull image" failure when attempting to create a Kubernetes Cluster using Container Server Extension 4.0
search cancel

"ERROR: failed to create cluster: failed to pull image" failure when attempting to create a Kubernetes Cluster using Container Server Extension 4.0

book

Article ID: 325570

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

Symptoms:
  • Attempting to create a Kubernetes Cluster using Container Server Extension 4.0 fails intermittently.
  • An image pull error due to a HTTP 408 response is reported:
[error while bootstrapping the machine [.../EPHEMERAL_TEMP_VM]; unable to wait for post customization phase [guestinfo.cloudinit.kind.cluster.creation.status] : [invalid postcustomization phase: [failed] for key [guestinfo.cloudinit.kind.cluster.creation.status] for vm [EPHEMERAL_TEMP_VM] due to :[<13>Nov 30 10:22:21 ...@System/administrator: + kind create cluster --config /root/kind-cluster-with-extramounts.yaml <13>Nov 30 10:22:21 ...@System/administrator: Creating cluster "kind" ... <13>Nov 30 10:22:21 ...@System/administrator: • Ensuring node image (kindest/node:v1.24.0) ... <13>Nov 30 10:26:17 ...@System/administrator: ✗ Ensuring node image (kindest/node:v1.24.0) <13>Nov 30 10:26:17 ...@System/administrator: ERROR: failed to create cluster: failed to pull image "kindest/node:v1.24.0@sha256:...": command "docker pull kindest/node:v1.24.0@sha256:..." failed with error: exit status 1 <13>Nov 30 10:26:17 ...@System/administrator: <13>Nov 30 10:26:17 ...@System/administrator: Command Output: Error response from daemon: error parsing HTTP 408 response body: invalid character '<' looking for beginning of value: "<html><body><h1>408 Request Time-out</h1>\nYour browser didn't send a complete request in time.\n</body></html>\n" <13>Nov 30 10:26:17 ...@System/administrator: ++ catch 1 114]]] during cluster creation


Environment

VMware Cloud Director 10.x

Cause

This issue can occur if there are issues reaching the internet from the EPHEMERAL_TEMP_VM to pull the required images.

Example causes could be:
  • Slow or intermittent internet connectivity.
  • The network IP Pool cannot resolve DNS (docker pull error)
  • The network MTU behind a firewall must set lower

Resolution

To resolve the issue ensure that there are no networking connectivity issues stopping the EPHEMERAL_TEMP_VM from reaching the internet.

Powered by Wolken Software