When I follow the kubernetes guide to install kubernetes on my local machine which runs fedora 27. I have already installed docker-ce 17.12(followed the Docker CE documentation).
bellow is the install output. is there any body can figure out what should I do to make kubernetes installed but also keep my docker-ce?
[ian#thinkpad ~]$ sudo LANG=en_US.UTF-8 dnf install kubernetes
Last metadata expiration check: 7:31:34 ago on Sat 13 Jan 2018 12:51:44 PM CST.
Error:
Problem: package kubernetes-node-1.7.3-1.fc27.x86_64 requires docker, but none of the providers can be installed
- package docker-ce-17.12.0.ce-1.fc27.x86_64 conflicts with docker provided by docker-2:1.13.1-42.git4402c09.fc27.x86_64
- package docker-ce-17.12.0.ce-1.fc27.x86_64 conflicts with docker provided by docker-2:1.13.1-26.gitb5e3294.fc27.x86_64
- problem with installed package docker-ce-17.12.0.ce-1.fc27.x86_64
- package kubernetes-1.7.3-1.fc27.x86_64 requires kubernetes-node = 1.7.3-1.fc27, but none of the providers can be installed
- conflicting requests
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages)
[ian#thinkpad ~]$ docker version
Client:
Version: 17.12.0-ce
API version: 1.35
Go version: go1.9.2
Git commit: c97c6d6
Built: Wed Dec 27 20:12:17 2017
OS/Arch: linux/amd64
Server:
Engine:
Version: 17.12.0-ce
API version: 1.35 (minimum version 1.12)
Go version: go1.9.2
Git commit: c97c6d6
Built: Wed Dec 27 20:14:50 2017
OS/Arch: linux/amd64
Experimental: false
[ian#thinkpad ~]$
Just requested for push of f27 update of kubernetes-1.9.1 [1] to the stable repository that allows to install either docker or docker-ce. It should take day or 2 to transit. Meantime you can install the kubernetes-node rpm from the update [1]. Tested that locally. Let me know if it does not work for you.
[1] https://bodhi.fedoraproject.org/updates/FEDORA-2018-d0a64cb26c
Regards
Jan
This is a known issue and an update is pending. Eventually, that will be in the updates set for F27 proper. In the meantime, you can get it from updates-testing, by doing:
sudo dnf --enablerepo=updates-testing install kubernetes
... and if that works for you, please add feedback on the pending update.
Related
I am setting up two Openshift Origins clusters running on RHEL 7.4.
The only thing that really shows me anything that is really wrong is this error log from the origin-pod from the docker node.
error: --deployment or OPENSHIFT_DEPLOYMENT_NAME is required
This leads me to think the deployment name is not getting passed to the container at startup. It then crashes not letting the deploy spin up. I see a ton of CNI errors but this is due to all containers assigned to this pod are killed as the origin-pod fails.
Here are the version of everything I could thing of that is needed to help find the true problem.
oc v3.6.0+c4dd4cf
kubernetes v1.6.1+5115d708d7
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server https://is-origins-tetration.cisco.com:8443
openshift v3.6.0+c4dd4cf
kubernetes v1.6.1+5115d708d7
docker version
Client:
Version: 1.12.6
API version: 1.24
Package version: docker-1.12.6-55.gitc4618fb.el7.x86_64
Go version: go1.8.3
Git commit: c4618fb/1.12.6
Built: Thu Aug 24 14:48:49 2017
OS/Arch: linux/amd64
Server:
Version: 1.12.6
API version: 1.24
Package version: docker-1.12.6-55.gitc4618fb.el7.x86_64
Go version: go1.8.3
Git commit: c4618fb/1.12.6
Built: Thu Aug 24 14:48:49 2017
OS/Arch: linux/amd64
oci-umount-1.12.6-55.gitc4618fb.el7.x86_64
oci-register-machine-0-3.11.1.gitdd0daef.el7.x86_64
oci-systemd-hook-0.1.12-1.git1e84754.el7.x86_64
Has anyone else seen this type of error?
Some person has install docker in my Redhat system . I want to know whether it is community edition or enterprise edition . How can i do so?
I know community edition is not for Redhat .
May be some person would have created centos.repo in Redhat and installed docker ce .
This is what
docker version
gives
When i do
"rpm -qif /usr/bin/docker"
With docker version command
CE : Comunity edition
EE : Entreprise edition
So 17.06.0-ce correspond to community edition
Client:
Version: 17.06.0-ce
API version: 1.30
Go version: go1.8.3
Git commit: 02c1d87
Built: Fri Jun 23 21:18:10 2017
OS/Arch: linux/amd64
Server:
Version: 17.06.0-ce
API version: 1.30 (minimum version 1.12)
Go version: go1.8.3
Git commit: 02c1d87
Built: Fri Jun 23 21:17:03 2017
OS/Arch: linux/amd64
Experimental: false
If you haven't ce or ee, it's because you have installed docker.io package, which is maintened by Ubuntu.
Version: 1.12.3
On Windows, you can also look about docker here :
EDIT
Docker Community Edition (Docker CE) is not supported on RHEL.
So, you have Docker entreprise edition.
See Docker documentation
Anyway, there are some ways to install docker-ce, but you will see docker community edition with docker version.
It seems to me that this is neither the Community Edition nor the Enterprise Edition. Based on the version and build date you posted, it looks like a build from the Red Hat Enterprise Linux 7 Extras channels (as the build time is identical to what is built into its docker client binary—but the time is different from the RPM build time, which confused me initially).
You should be able to double-check using
rpm -qif /usr/bin/docker
and compare the package signer with the official Red Hat product signing keys.
Software provided in the Red Hat Enterprise Linux Extras channels is fully supported by Red Hat. (The difference from other channels is the update frequency, not the support coverage.) In this sense, these builds are closer to the Enterprise Edition from Docker, Inc., because there is vendor support (unlike the Community Edition, which is, I think, unsupported).
Disclaimer: While I work for Red Hat, you need to review the agreements for yourself to determine support coverage etc., and contact customer support in case there are open questions.
Just execute docker version. All before Docker version 17.03 did not have a -ce or -ee in the version.
# docker version
Client:
Version: 17.03.0-ce
API version: 1.26
Go version: go1.7.5
Git commit: 60ccb22
Built: Thu Feb 23 11:07:40 2017
OS/Arch: linux/amd64
Server:
Version: 17.03.0-ce
API version: 1.26 (minimum version 1.12)
Go version: go1.7.5
Git commit: 60ccb22
Built: Thu Feb 23 11:07:40 2017
OS/Arch: linux/amd64
Experimental: false
We are running Openshift Origin which got installed by using the Ansible playbooks.
This by default installed docker 1.9.1, now we have to upgrade it to the latest version because of frequent crashes of docker.
But seems like Origin package dependent on docker 1.9.1.
So, How do I upgrade docker to latest version which is recognizable by Origin?
Origin 1.4.1, RHEL 7.2
Origin 1.4.1 requires Docker 1.12 and RedHat/CentOS 7.3. (the docs are for OCP 3.4 but they match with Origin 1.4)
Upgrading RHEL to 7.3 should also let you install Docker 1.12:
(master-prod-public)root#master1:~# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.3 (Maipo)
(master-prod-public)root#master1:~# docker version
Client:
Version: 1.12.6
API version: 1.24
Package version: docker-common-1.12.6-16.el7.x86_64
Go version: go1.7.4
Git commit: 3a094bd/1.12.6
Built: Tue Mar 21 13:30:59 2017
OS/Arch: linux/amd64
Server:
Version: 1.12.6
API version: 1.24
Package version: docker-common-1.12.6-16.el7.x86_64
Go version: go1.7.4
Git commit: 3a094bd/1.12.6
Built: Tue Mar 21 13:30:59 2017
OS/Arch: linux/amd64
Also check if there are any leftover versionlocks:
(m
aster-prod-public)root#master1:~# yum versionlock
Loaded plugins: search-disabled-repos, versionlock
# list of locked packages...
versionlock list done
I just installed docker on my windows 10 server,
Installation went fine but I can't seem to get images from central docker repo.
those are my specs:
c:\>docker version
Client:
Version: 1.13.0
API version: 1.25
Go version: go1.7.3
Git commit: 49bf474
Built: Wed Jan 18 16:20:26 2017
OS/Arch: windows/amd64
Server:
Version: 1.13.0
API version: 1.25 (minimum version 1.12)
Go version: go1.7.3
Git commit: 49bf474
Built: Wed Jan 18 16:20:26 2017
OS/Arch: linux/amd64
Experimental: true
This is my test command:
c:\>docker run hello-world
Unable to find image 'hello-world:latest' locally
docker: Error response from daemon: Get https://registry-1.docker.io/v2/: remote error: tls: access denied.
See 'docker run --help'.
This is what I get when running curl on that repo:
c:\>curl -k https://registry-1.docker.io/v2/
{"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":null}]}
I guess that there is something to do with my company DNS/Network,
did anyone encounter this issue on windows?
You need to set your proxy env variables.
[Environment]::SetEnvironmentVariable("HTTP_PROXY", "http://username:password#proxy:port/", [EnvironmentVariableTarget]::Machine)
Restart-Service docker
Check this for reference: https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-docker/configure-docker-daemon
And more common:
https://docs.docker.com/engine/admin/systemd/#http-proxy
As I replied to #Falco Alexander I got some PowerShell errors, But The proxy was already set in my env. variables.
What finally did the trick was to set the proxy inside the docker GUI:
And then restart the service.
I'm behind a corporate firewall and have installed Docker on an Ubuntu 14.04 LTS server. Following instructions at http://docs.docker.com/linux/step_one/.
Things seemed to be OK:-
$ docker version
Client:
Version: 1.9.1
API version: 1.21
Go version: go1.4.2
Git commit: a34a1d5
Built: Fri Nov 20 13:12:04 UTC 2015
OS/Arch: linux/amd64
Server:
Version: 1.9.1
API version: 1.21
Go version: go1.4.2
Git commit: a34a1d5
Built: Fri Nov 20 13:12:04 UTC 2015
OS/Arch: linux/amd64
... but I can't pull and run any images. Example:-
$ docker run hello-world
gives:
Error while pulling image: Get
https://index.docker.io/v1/repositories/library/hello-world/images:
x509: certificate is valid for FG3K6C3A15800002, not index.docker.io
Have spent ages searching around - I don't understand what the issue is - I've set http_proxy and https_proxy env vars but not sure what to try next. The docs don't mention any certificate requirements.
Any help appreciated!
The problem may be the proxy. If you are using a proxy to access the internet, you have to change the file /etc/default/docker and put your proxy on it.
export http_proxy="http://proxy_ip:proxy_port"
export https_proxy="http://proxy_ip:proxy_port"
After do it, restart the service:
sudo service docker restart
It works to me.
Hey Pravins I have the same issue, with my docker 1.11.2 It seems is not taken proxy settings from /etc/default/docker and from env neighter.
So what I did was what it says here
http://docs.master.dockerproject.org/engine/admin/systemd/#http-proxy
Many Linux distributions use systemd to start the Docker daemon.
You need check if the docker.service uses an EnvironmentFile, and/or You can customize the Docker daemon options using override files as explained in the HTTP Proxy example below.