My Oracle Support Banner

UIM CN: kubeadm init Fails with CreatePodSandboxError on Offline Machine (Doc ID 2954055.1)

Last updated on JUNE 07, 2023

Applies to:

Oracle Communications Unified Inventory Management - Version 7.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Customer configuring kubernetes on an offline (not having internet connection) machine & kubeadm init fails with error below:

"Error syncing pod, skipping" err="failed to \"CreatePodSandbox\" for \"kube-apiserver-uim-tnd-topo-app_kube-system\" with

CreatePodSandboxError: \"Failed to create sandbox for pod \\\"kube-apiserver-uim-tnd-topo-app_kube-system\\\"

: rpc error: code = Unknown desc = creating pod sandbox with name \\\"k8s_kube-apiserver-uim-tnd-topo-app_kube-system\\\"

: initializing source docker://registry.k8s.io/pause:3.6: pinging container registry registry.k8s.io: Get \\\"https://registry.k8s.io/v2/\\\": dial tcp: lookup registry.k8s.io on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address\"" pod="kube-system/kube-apiserver-uim-tnd-topo-app"

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.