-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest docker version breaks kubelet in 1.5.0-alpha.3 #13281
Comments
Running on Fedora 25 |
Follow up to #13219 |
I tried with the latest origin master and I get the same error (on fedora 25). However, I don't see the error on Docker for Mac. |
I am seeing the issue with Docker for Mac 17.03.0-ce, commit 60ccb22. oc version |
@justinclayton are you not able to run pods at all? |
Sorry, I'm in the wrong issue. I'm trying to run |
@justinclayton you'll need an oc binary from the origin master |
On the latest Docker for Mac I'm experiencing issues running |
@zmhassan what are your versions of docker and oc, and do you see any events in the openshift-infra namespace about the metrics pods? |
|
@zmhassan you need the latest origin master. If you somehow have access to a cluster, you can build your own binary using https://github.com/csrwng/build-origin |
Hi @csrwng I could build from source as I already have all the openshift source. This step your suggestion is only going to create binary that I can easily download from github or build myself. |
So if I build latest it should work is what your saying? |
yes |
Nope doesn't work.
|
@zmhassan what version of the images are you using ? (Are you specifying --version=blah with |
@zmhassan so I tried locally and I did see the errors but eventually pods ran and metrics came up. |
Kube issue: kubernetes/kubernetes#42492 |
It looks like something changed in the kubelet recently that broke things. Running cluster up with /cc @derekwaynecarr |
When I try oc cluster up --version=v1.5.0-alpha.3 and create a project, the build fail immediately with error: cannot connect to the server: open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory I then tried v1.5.0-alpha.3 client tools with oc cluster up --version=v1.5.0-alpha.3 fails immediately with -- Checking OpenShift client ... OK Looks like I'm stuck. I was trying to use origin for an internal class in a week. Is there a way to install an older docker engine on CentOS? |
I'm still having issues and I'm not seeing metrics show up at all. |
I managed to get it all working. Thank you. |
got a little further, but the issue is now during build: |
@shveik is your registry up and running? |
great question, please bare with me since it's my first day playing with this, and i am following instructions here: https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md#macos-with-docker-for-mac so, looks like the registry is running: however, the login is not working, since OPENSHIFT_TOKEN is null: i do have an insecure registry configured for 172.30.0.0/16 |
@shveik did you specify --version=v1.5.0-alpha.3 with 'oc cluster up'? If not, try that first |
If you are logged in as system:admin, you will not have a token, since you are logged in via certificate. If you need a token, you need to be a regular user. |
All my attempts (even with previous Alpha versions) to get beyond the
Docker version issues have failed. I ended up installing an old Docker 1.13
version from https://yum.dockerproject.org/. With that, v1.5.0-rc.0 has
worked just fine. I hope it stays that way. Will need that system for an
intro class to OpenShift next week ...
Best,
Michael
…On Thu, Mar 16, 2017 at 12:34 PM, Alex Reznik ***@***.***> wrote:
great question, please bare with me since it's my first day playing with
this, and i am following instructions here: https://github.com/openshift/
origin/blob/master/docs/cluster_up_down.md#macos-with-docker-for-mac
so, looks like the registry is running:
➜ ~ oc get svc docker-registry -n default
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
docker-registry 172.30.1.1 5000/TCP 16m
however, the login is not working, since OPENSHIFT_TOKEN is null:
➜ ~ OPENSHIFT_TOKEN=$(oc whoami -t)
error: no token is currently in use for this session
i do have an insecure registry configured for 172.30.0.0/16
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13281 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJqqVDBDyEZHGrZQEfbhZ7zG6SM6sDo5ks5rmY7DgaJpZM4MVd22>
.
|
@csrwng that was it, thank you. so when running with version, here is the output, so basically, it's the client and server versions that differ: Server https://127.0.0.1:8443 and here is without version: Server https://127.0.0.1:8443 |
how to solve that when using the server binary instead of using I use |
@mbechauf on CentOS for installing Docker, use |
I see a similar issue with current master: Build is pending when I try to create a new ruby-ex app. See following message in Build -> Last Build -> Events tab: Time Severity Reason Message |
The kubelet is still not working with the new Docker version string. Easiest thing to do is to downgrade Docker. |
Got stuck on the first tutorial. OS: Fedora25 Version:
The error:
Tutorial worked on:
|
Which docker version should I use to make it work, while we don't have the [final] working solution? |
OpenShift Origin 1.5 should use Docker 1.12. |
On mac os with latest Docker for Mac Version 17.03.1-ce-mac5 (16048) I was able to
changing the
The deployment just automatically ran and succeeded on the older version. |
An alternative for now is also to downgrade to Docker 1.13.1 for Mac: |
We will need to cherry-pick kubernetes/kubernetes#44068, probably to solve the problem |
I'll pick it up once the upstream PR merges and the rebase lands |
I've cherry-picked the upstream fix in attached PR. |
@csrwng @jimmidyson
The text was updated successfully, but these errors were encountered: