kubeadm: kubeadm init (offline mode) stuck on pulling images
BUG REPORT
Versions
v1.10.0
kubeadm version (use kubeadm version):
v1.10.0
Environment:
- Kubernetes version 1.10.0
- Cloud provider or hardware configuration: On premise (OFFLINE)
- OS (e.g. from /etc/os-release): Centos
- Kernel (e.g.
uname -a): 3.10.0-514 - Others: Docker images are pre-loaded
What happened?
Running the same process on the internet works flawless, however on offline mode my kubeadm init process is stuck on pulling images.
On the /var/log/messages I can see a lots of retries to connect to 127.0.0.1:6443 while this port doesn’t exists on the system.
The following docker containers exists when running docker ps:
controller-mananger
etcd
4 x pause
What you expected to happen?
To run exactly as if I were online and succeed with cluster deployment
How to reproduce it (as minimally and precisely as possible)?
- Create a local RPM repository that have the v1.10.0 packages
- Set your Centos to work with that repository
- Download all the docker containers that v1.10.0 requires and load them to your machine
- Go offline completely
- Disable DNS resolving
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 27 (4 by maintainers)
I’ve done testing a similar isolated environment on an internet machine where the network connection was physically disconnected - tldr - it failed with the same results as I had before.
However this time I can provide a very detailed logs and process as it’s a machine on the internet, so here it goes:
Command history
1 - Installed docker
2 - Loading docker images for offline use (Downloaded with docker pull the following images)
3 - Installed kubectl, kubeadm, kubelet
4 - Initiated the kubeadm init process
Logs from kubeadm
Logs from /var/log/messages
What are the specs of this machine? Plenty of resources to spare? Does it meet the minimum requirements listed here https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/#before-you-begin ?
I get the exact same situation when I use a vm with .5gB of ram and when i increase it to 2gB everything works fine.