(1)docker簡介:
起源
-
環境管理復雜 - 從各種OS到各種中間件到各種app, 一款產品能夠成功作為開發者需要關心的東西太多,且難於管理,這個問題幾乎在所有現代IT相關行業都需要面對。
-
雲計算時代的到來 - AWS的成功, 引導開發者將應用轉移到 cloud 上, 解決了硬件管理的問題,然而中間件相關的問題依然存在 (所以openstack HEAT和 AWS cloudformation 都着力解決這個問題)。開發者思路變化提供了可能性。
-
虛擬化手段的變化 - cloud 時代采用標配硬件來降低成本,采用虛擬化手段來滿足用戶按需使用的需求以及保證可用性和隔離性。然而無論是KVM還是Xen在 docker 看來,都在浪費資源,因為用戶需要的是高效運行環境而非OS, GuestOS既浪費資源又難於管理, 更加輕量級的LXC更加靈活和快速
-
LXC的移動性 - LXC在 linux 2.6 的 kernel 里就已經存在了,但是其設計之初並非為雲計算考慮的,缺少標准化的描述手段和容器的可遷移性,決定其構建出的環境難於遷移和標准化管理(相對於KVM之類image和snapshot的概念)。docker 就在這個問題上做出實質性的革新。這是docker最獨特的地方。
-
Automating the packaging and deployment of applications
-
Creation of lightweight, private PAAS environments
-
Automated testing and continuous integration/deployment
-
Deploying and scaling web apps, databases and backend services
-
構建標准化的運行環境,現有的方案大多是在一個baseOS上運行一套puppet/chef,或者一個image文件,其缺點是前者需要base OS許多前提條件,后者幾乎不可以修改(因為copy on write 的文件格式在運行時rootfs是read only的)。並且后者文件體積大,環境管理和版本控制本身也是一個問題。
-
PaaS環境是不言而喻的,其設計之初和dotcloud的案例都是將其作為PaaS產品的環境基礎
-
因為其標准化構建方法(buildfile)和良好的REST API,自動測試和持續集成/部署能夠很好的集成進來
-
因為LXC輕量級的特點,其啟動快,而且docker能夠只加載每個container變化的部分,這樣資源占用小,能夠在單機環境下與KVM之類的虛擬化方案相比能夠更加快速和占用更少資源
(2) docker的安裝
1.1 如果是Centos7,直接使用sudo yum install -y docker
1.2 如果是Centos6,sudo yum install -y http://mirrors.yun-idc.com/epel/6/i386/epel-release-6-8.noarch.rpm
sudo yum install -y docker-io
(3)docker的基本操作
1.1 系統條件,本系統使用的linux操作系統是Centos7_x64
1.2 啟動docker,service docker start
1.3 演示從Docker Hub上下載最新版本的ubuntu
命令: sudo docker pull ubuntu,會有如下的信息提示:
[kass@localhost ~]$ sudo docker pull ubuntu
Using default tag: latest
Trying to pull repository docker.io/library/ubuntu ... latest: Pulling from library/ubuntu
c2a0e656b13b: Pull complete
a1918483ff2d: Pull complete
19f3070b96b2: Pull complete
0930cd7fba20: Pull complete
8e5b7248472b: Pull complete
Digest: sha256:46fb5d001b88ad904c5c732b086b596b92cfb4a4840a3abd0e35dbb6870585e4
Status: Downloaded newer image for docker.io/ubuntu:latest
1.4 使用下載的鏡像創建一個容器,在其中運行bash應用,具體執行結果如下:
[kass@localhost ~]$ sudo docker run -t -i ubuntu /bin/bash
[sudo] password for kass:
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.
1.5 使用docker images 命令查看本地主機上已有的鏡像,及添加一個新的ubuntu:latest鏡像標簽
具體的操作命令及信息如下:
[kass@localhost ~]$ sudo docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
docker.io/ubuntu latest 8e5b7248472b 2 weeks ago 122 MB
[kass@localhost ~]$ sudo docker tag docker.io/ubuntu:latest ubuntu:latest
[kass@localhost ~]$ sudo docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
ubuntu latest 8e5b7248472b 2 weeks ago 122 MB
docker.io/ubuntu latest 8e5b7248472b 2 weeks ago 122 MB
1.6 查看鏡像的詳細信息
[kass@localhost ~]$ sudo docker inspect 8e5b7248472b
[sudo] password for kass:
[
{
"Id": "8e5b7248472b1cf370e8b181c357148a5aff33c0b8da2ba133701f599de15a84",
"RepoTags": [
"docker.io/ubuntu:latest",
"ubuntu:latest"
],
"RepoDigests": [],
"Parent": "0930cd7fba20b2f6a84c3abc1918b4e159b123c1a3b787c0a9bea874e4f7e40b",
"Comment": "",
"Created": "2016-05-27T14:15:02.359284074Z",
"Container": "b8bd6a8e8874a87f626871ce370f4775bdf598865637082da2949ee0f4786432",
"ContainerConfig": {
"Hostname": "914cf42a3e15",
"Domainname": "",
"User": "",
"AttachStdin": false,
"AttachStdout": false,
"AttachStderr": false,
"Tty": false,
"OpenStdin": false,
"StdinOnce": false,
"Env": [],
"Cmd": [
"/bin/sh",
"-c",
"#(nop) CMD [\"/bin/bash\"]"
],
"Image": "b873f334fa5259acb24cf0e2cd2639d3a9fb3eb9bafbca06ed4f702c289b31c0",
"Volumes": null,
"WorkingDir": "",
"Entrypoint": null,
"OnBuild": null,
"Labels": {}
},
"DockerVersion": "1.9.1",
"Author": "",
"Config": {
"Hostname": "914cf42a3e15",
"Domainname": "",
"User": "",
"AttachStdin": false,
"AttachStdout": false,
"AttachStderr": false,
"Tty": false,
"OpenStdin": false,
"StdinOnce": false,
"Env": [],
"Cmd": [
"/bin/bash"
],
"Image": "b873f334fa5259acb24cf0e2cd2639d3a9fb3eb9bafbca06ed4f702c289b31c0",
"Volumes": null,
"WorkingDir": "",
"Entrypoint": null,
"OnBuild": null,
"Labels": {}
},
"Architecture": "amd64",
"Os": "linux",
"Size": 0,
"VirtualSize": 121963951,
"GraphDriver": {
"Name": "devicemapper",
"Data": {
"DeviceId": "6",
"DeviceName": "docker-253:1-34403904-8e5b7248472b1cf370e8b181c357148a5aff33c0b8da2ba133701f599de15a84",
"DeviceSize": "107374182400"
}
}
}
]
1.7 詳細搜索
sudo docker -f {{".Architecture"}} 8e5 //8e5就是8e5b7248472b 是鏡像的ID
1.8 搜索鏡像
[kass@localhost ~]$ sudo docker search mysql
INDEX NAME DESCRIPTION STARS OFFICIAL AUTOMATED
docker.io docker.io/mysql MySQL is a widely used, open-source relati... 2493 [OK]
docker.io docker.io/mysql/mysql-server Optimized MySQL Server Docker images. Crea... 158 [OK]
docker.io docker.io/centurylink/mysql Image containing mysql. Optimized to be li... 45 [OK]
docker.io docker.io/sameersbn/mysql 36 [OK]
docker.io docker.io/appcontainers/mysql Centos/Debian/Ubuntu Based Customizable My... 7 [OK]
docker.io docker.io/marvambass/mysql MySQL Server based on Ubuntu 14.04 6 [OK]
docker.io docker.io/alterway/mysql Docker Mysql 2 [OK]
docker.io docker.io/azukiapp/mysql Docker image to run MySQL by Azuki - http:... 2 [OK]
docker.io docker.io/drupaldocker/mysql MySQL for Drupal 2 [OK]
docker.io docker.io/yfix/mysql Yfix docker built mysql 2 [OK]
docker.io docker.io/bahmni/mysql Mysql container for bahmni. Contains the ... 1 [OK]
docker.io docker.io/phpmentors/mysql MySQL server image 1 [OK]
docker.io docker.io/sin30/mysql MySQL images with my own config files. 1 [OK]
docker.io docker.io/tetraweb/mysql 1 [OK]
docker.io docker.io/ahmet2mir/mysql This is a Debian based image with MySQL se... 0 [OK]
docker.io docker.io/akilli/mysql akilli/base based MySQL image 0 [OK]
docker.io docker.io/cloudposse/mysql Improved `mysql` service with support for ... 0 [OK]
docker.io docker.io/dockerizedrupal/mysql docker-mysql 0 [OK]
docker.io docker.io/jeffutter/mysql-no_volumes Images based on the official mysql images ... 0 [OK]
docker.io docker.io/kardasz/mysql Debian 8, MySQL 5.7 0 [OK]
docker.io docker.io/lancehudson/docker-mysql MySQL is a widely used, open-source relati... 0 [OK]
docker.io docker.io/nanobox/mysql MySQL service for nanobox.io 0 [OK]
docker.io docker.io/projectomakase/mysql Docker image for MySQL 0 [OK]
docker.io docker.io/tozd/mysql MySQL (MariaDB fork) Docker image. 0 [OK]
docker.io docker.io/vukor/mysql Build for MySQL. Project available on http... 0 [OK]
1.9 刪除鏡像
1.9.1 通過name刪除鏡像
[kass@localhost ~]$ sudo docker rmi docker.io/ubuntu
Untagged: docker.io/ubuntu:latest
[kass@localhost ~]$ sudo docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
ubuntu latest 8e5b7248472b 2 weeks ago 122 MB
1.9.2 通過鏡像ID刪除文件
這種方式,會先嘗試刪除所有指向該鏡像的標簽,然后刪除該鏡像本身
[kass@localhost ~]$ sudo docker rmi docker.io/ubuntu
2.0 創建鏡像
[kass@localhost ~]$ sudo docker run -ti ubuntu /bin/bash
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.
root@bfda0c922239:/# touch test
root@bfda0c922239:/# exit
exit
[kass@localhost ~]$ sudo docker commit -m "Add a new file" -a "Docker Newbee" 8e5b7248472b test
Error response from daemon: no such id: 8e5b7248472b
[kass@localhost ~]$ sudo docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
ubuntu latest 8e5b7248472b 2 weeks ago 122 MB
[kass@localhost ~]$ sudo docker commit -m "Add a new file" -a "Docker Newbee" bfda0c922239 test
4521126f01b2bdf6816929a82cd428bfc2da50119f4c1afc19f751fec71d510c
[kass@localhost ~]$ sudo docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
test latest 4521126f01b2 6 seconds ago 122 MB
ubuntu latest 8e5b7248472b 2 weeks ago 122 MB
2.1 存儲鏡像、載入鏡像
2.1.1 存儲鏡像
[kass@localhost ~]$ sudo docker save -o test.zip test
2.1.2 載入鏡像
[kass@localhost ~]$ sudo docker load < test.zip
或者
[kass@localhost ~]$ sudo docker load --input test.zip
note:使用sudo的時候如果提示permission denied,將當前用戶切換為root身份,
然后編輯/etc/sudoers 文件, 在root ALL=(ALL) ALL下面添加 kass ALL=(ALL) ALL