New docker images version, errors #8
Comments
|
Can you provide some logs or insights as to what was breaking? |
|
for example I got this: and Master 1 gave an error installing it, the installation of the workers went ok in all cases but the master PI's always gave errors but where also different every time I tried. Also now when I try to access them from my machine I get the message: gibson$ kubectl get nodes |
|
Hmm tried the old one now but its also giving me errors... Interesting is that Master VIP is marked as Master 1 but this one is hanging, see above. |
|
Maybe if you are having some time, are you on a chatting platform like Gitter, Hangouts? |
|
In hindsight I should have referred to this: https://v1-16.docs.kubernetes.io/docs/setup/production-environment/container-runtimes/ Was that first certificate error because of the old kubernetes configuration file from the previous cluster? |
|
What I did was reinstall all the SD cards using the make build and modified the parameters according for worker and master. I kept the old SSH file and img file that was in the output file as these are working and didn't need to recreate those. I also can use the ssh to login in the machine so that's all fine. Was that first certificate error because of the old kubernetes configuration file from the previous cluster?
What I will do is try again with the new repo and report back with the logs and all. |
|
Please. Sorry I don’t have a huge amount of time to troubleshoot heaps now, quite busy at work. Can jump in here and respond every now and again. |
|
So I have some logs, the workers seem to work well and installation goes smooth but the problems are with the masters. Output Master1 Master2 went well and finished installation: Master3 output: Hope you see what could go wrong and what to try? But its not clear for me from the logs what is exactly failing of the docker commands... |
|
Couple of things that stand out to me. I’m not sure what And this: So if you revert the docker version back to 18.09, what happens do you get consistent results? Does it always have two successful masters and one failed one? |
|
Hmm it looks the remote version issue is regarding a kubeadm issue I will now give a try with the previous docker-ce 18.09 version that also uses the export fix we did |
|
So I tried to old one and still doesn't work, only 1 master is installing correctly in this case Master3 Master3 output Master2 output Master1 output In these error messages you see again the message: but also this error: That is quite weird why it would throw that error message... What do you think? |
|
I really have no clue anymore, I tried on other thing some people had issues with the kubeadm and for them it got fixed when running with sudo. So I tried it and now its booting again, all masters are up |
|
What the? Was that with the new version of docker or old? |
|
Sounds like a bug somewhere in kubeadm! |
|
Facing similar issue.
Docker version: kubeadm version
But kubelet is running and its joining the cluster. |
For me I used the old one with the export docker api fix and running the sudo kubeadm init |
|
I still have no idea how the Super super interesting. I mean we can patch it with that and see if that works, but really weird. |
|
well indeed I also didn't get it but gave it a go and worked, so for the old version of docker + the docker env fix API + making the config sudo will now work again. For using the new docker version, it raises other errors and I didn't know why and how to solve that... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the last commit we changed the below versions for the docker installation
I have now tried it in combination of the project and it's now breaking the installation. I needed to reinstall all the raspberry PI's and used the project again.
I have retried it a couple of times with different issues but one that was interesting is that the Nodes overview only contained 1 Master Type node and the other Master nodes didn't have a type.
So I suggest to revert the change and add the export var again for the docker API so at least its working. Then from there we need to debug and see why its not working with the latest Docker version 5:19 but I think you have to do this as I'm not cable of understanding what's going wrong.
The text was updated successfully, but these errors were encountered: