Docker Community Forums

Share and learn in the Docker community.

Upgrading docker from 1.10 to 1.12 on CentOS 7.2


(Bluemind2005) #1

Hello Docker,

I installed docker with yum by executing command
yum install docker
Interesting I want now to update to latest version of docker which 1.12. To my surprise when I execute the following command
yum-config-manager --add-repo

It said to me that I have installed docker 1.10 and docker-engine is not installed !

Do they mean I have installed complete package as in docker-swarm, docker-compose, docker =-engine and I was trying to upgrade just one component of it?

Nevertheless, I am looking for instruction on how to upgrade as docker 1.10 is pretty old version and I would really like to on latest and greatest version 1.12

Currently I am on docker 1.10

[root@docker1 ~]# docker info
Containers: 11
Running: 0
Paused: 0
Stopped: 11
Images: 5
Server Version: 1.10.3
Storage Driver: devicemapper
Pool Name: docker-253:0-135501105-pool
Pool Blocksize: 65.54 kB
Base Device Size: 10.74 GB
Backing Filesystem: xfs
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 556.7 MB
Data Space Total: 107.4 GB
Data Space Available: 48.11 GB
Metadata Space Used: 1.43 MB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.146 GB
Udev Sync Supported: true
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
WARNING: Usage of loopback devices is strongly discouraged for production use. Either use --storage-opt dm.thinpooldev or use --storage-opt dm.no_warn_on_loop_devices=true to suppress this warning.
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.107-RHEL7 (2015-10-14)
Execution Driver: native-0.2
Logging Driver: journald
Volume: local
Network: null host bridge
Kernel Version: 3.10.0-327.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 2
CPUs: 1
Total Memory: 1.462 GiB
Name: docker1
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Registries: (secure)
[root@docker1 ~]#

I don’t see any documentation so now relying on community experts.

Please guide me.


(Bluemind2005) #2

Not sure if this correct method but I uninstalled docker 1.10 by yum remove docker(all relevant packages). Deleted /var/lib/docker/* and now when I try to install with command

sudo yum install docker-engine

Error message below:
Is this ok [y/d/N]: y
Downloading packages:
warning: /var/cache/yum/x86_64/7/packages.docker.com_1.11_yum_repo_main_centos_7/packages/docker-engine-1.11.2.cs3-1.el7.centos.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID 6238f52e: NOKEY

Public key for docker-engine-1.11.2.cs3-1.el7.centos.x86_64.rpm is not installed

I tried the bwlow to install gpg key but no use:

[jim@docker1 ~]$ sudo wget
--2016-07-22 14:46:26--
Resolving (
Connecting to (||:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1648 (1.6K) [application/pgp-keys]
Saving to: ‘gpg’

100%[====================================================================================================>] 1,648       --.-K/s   in 0s      

2016-07-22 14:46:27 (137 MB/s) - ‘gpg’ saved [1648/1648]

[jim@docker1 ~]$ ls -l
total 4
drwxrwxr-x. 3 jim  jim    26 Jul 21 14:57 Documents
-rw-r--r--. 1 root root 1648 Jun  2 21:10 gpg
drwxrwxr-x. 2 jim  jim    23 Jul 22 00:47 web
[jim@docker1 ~]$ gpd --import gpg 
-bash: gpd: command not found
[jim@docker1 ~]$ gpg --import gpg 
gpg: directory `/home/jim/.gnupg' created
gpg: new configuration file `/home/jim/.gnupg/gpg.conf' created
gpg: WARNING: options in `/home/jim/.gnupg/gpg.conf' are not yet active during this run
gpg: keyring `/home/jim/.gnupg/secring.gpg' created
gpg: keyring `/home/jim/.gnupg/pubring.gpg' created
gpg: /home/jim/.gnupg/trustdb.gpg: trustdb created
gpg: key 2C52609D: public key "Docker Release Tool (releasedocker) <>" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)

Not sure why the standard docker documentation doesn’t work !