For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!
Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.
Hello.
Thanks for sharing.
I receive the following error message:
/vagrant/scripts/kubeadm-setup-master.sh: Login to container-registry.oracle.com
Username (japablo@mercuritech.com):
Password:
Login Succeeded
/vagrant/scripts/kubeadm-setup-master.sh: Setup Master node -- be patient!
/vagrant/scripts/kubeadm-setup-master.sh: kubeadm-setup.sh did not complete successfully
Last lines of kubeadm-setup.log:
Starting to initialize master node ...
Checking if env is ready ...
Checking whether docker can pull busybox image ...
Checking access to container-registry.oracle.com/kubernetes ...
[ERROR] Please login with valid credential to the container-registry.oracle.com/kubernetes
# docker login container-registry.oracle.com/kubernetes
All logins checked (both oracle & github)
VBox + extensions updated (today)
What could be wrong?
BR!!!
Hello.Thanks for sharing.I receive the following error message: /vagrant/scripts/kubeadm-setup-master.sh: Login to container-registry.oracle.comUsername (japablo@mercuritech.com):Password:Login Succeeded/vagrant/scripts/kubeadm-setup-master.sh: Setup Master node -- be patient!/vagrant/scripts/kubeadm-setup-master.sh: kubeadm-setup.sh did not complete successfullyLast lines of kubeadm-setup.log:Starting to initialize master node ...Checking if env is ready ...Checking whether docker can pull busybox image ...Checking access to container-registry.oracle.com/kubernetes ...[ERROR] Please login with valid credential to the container-registry.oracle.com/kubernetes # docker login container-registry.oracle.com/kubernetesAll logins checked (both oracle & github)VBox + extensions updated (today)What could be wrong?BR!!!
Hi, you should "manually" accept "Oracle Standard Terms and Restrictions" before trying to setup master node. Login with your credentials on https://container-registry.oracle.com/ , then enter "Container Services" business area. Click on "Continue" button to accept the license statement.
Go back to your environment and retry.
Best Regards,
Marzio
Hi, you should "manually" accept "Oracle Standard Terms and Restrictions" before trying to setup master node. Login with your credentials on https://container-registry.oracle.com/ , then enter "Container Services" business area. Click on "Continue" button to accept the license statement.Go back to your environment and retry.Best Regards,Marzio
Hello Marzio.
It works... perfect!!!, thanks.
[vagrant@master ~]$ kubectl cluster-info
Kubernetes master is running at https://192.168.99.100:6443
KubeDNS is running at https://192.168.99.100:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
[vagrant@master ~]$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
master.vagrant.vm Ready master 1h v1.9.1+2.1.5.el7
worker1.vagrant.vm Ready <none> 17m v1.9.1+2.1.5.el7
worker2.vagrant.vm Ready <none> 3m v1.9.1+2.1.5.el7
[vagrant@master ~]$ kubectl get pods --namespace=kube-system
NAME READY STATUS RESTARTS AGE
etcd-master.vagrant.vm 1/1 Running 0 1h
kube-apiserver-master.vagrant.vm 1/1 Running 0 1h
kube-controller-manager-master.vagrant.vm 1/1 Running 0 1h
kube-dns-855949bbf-mjmmx 3/3 Running 0 1h
kube-flannel-ds-2zf2z 1/1 Running 0 17m
kube-flannel-ds-6fm9t 1/1 Running 0 3m
kube-flannel-ds-lf86k 1/1 Running 0 1h
kube-proxy-596rh 1/1 Running 0 1h
kube-proxy-bqwkp 1/1 Running 0 17m
kube-proxy-tsjms 1/1 Running 0 3m
kube-scheduler-master.vagrant.vm 1/1 Running 0 1h
kubernetes-dashboard-7c966ddf6d-cttgb 1/1 Running 0 1h
Best Regards!!!
It worked for me.
But after starting the master I had to execute :
[root@master vagrant]# sudo cp /etc/kubernetes/admin.conf $HOME/
[root@master vagrant]# sudo chown $(id -u):$(id -g) $HOME/admin.conf
[root@master vagrant]# export KUBECONFIG=$HOME/admin.conf
Hello
I have done everiting like described but the "kubeadm-setup-master.sh" fails .... can someone help?
----------------------------------
[vagrant@master ~]$ su root
[root@master vagrant]# /vagrant/scripts/kubeadm-setup-master.sh
Username: marcus.juettner@elaxy.com
WARNING! Your password will be stored unencrypted in /root/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store
Checking br_netfilter module ...
Checking sysctl variables ...
Enabling kubelet ...
Created symlink from /etc/systemd/system/multi-user.target.wants/kubelet.service to /etc/systemd/system/kubelet.service.
Check successful, ready to run 'up' command ...
Waiting for kubeadm to setup master cluster...
Please wait ...
[ERROR] kubeadm init failed
invalid configuration: kind and apiVersion is mandatory information that needs to be specified in all YAML documents
[root@master vagrant]#
-----------------------------------------------------------
Bye
Marcus
HelloI have done everiting like described but the "kubeadm-setup-master.sh" fails .... can someone help?----------------------------------[vagrant@master ~]$ su root[root@master vagrant]# /vagrant/scripts/kubeadm-setup-master.sh/vagrant/scripts/kubeadm-setup-master.sh: Login to container-registry.oracle.comUsername: marcus.juettner@elaxy.comPassword:WARNING! Your password will be stored unencrypted in /root/.docker/config.json.Configure a credential helper to remove this warning. Seehttps://docs.docker.com/engine/reference/commandline/login/#credentials-storeLogin Succeeded/vagrant/scripts/kubeadm-setup-master.sh: Setup Master node -- be patient!/vagrant/scripts/kubeadm-setup-master.sh: kubeadm-setup.sh did not complete successfullyLast lines of kubeadm-setup.log:Checking br_netfilter module ...Checking sysctl variables ...Enabling kubelet ...Created symlink from /etc/systemd/system/multi-user.target.wants/kubelet.service to /etc/systemd/system/kubelet.service.Check successful, ready to run 'up' command ...Waiting for kubeadm to setup master cluster...Please wait ...[ERROR] kubeadm init failedinvalid configuration: kind and apiVersion is mandatory information that needs to be specified in all YAML documents[root@master vagrant]#-----------------------------------------------------------ByeMarcus
See: https://github.com/oracle/vagrant-boxes/issues/114 for a solution.
Thanx a lot .... worked!