ubuntu環境下docker安裝步驟

本文是根據docker官方文檔翻譯,原文:https://docs.docker.com/engine/installation/linux/ubuntulinux/

Docker 支持如下 Ubuntu 系統:php

  • Ubuntu Xenial 16.04 (LTS)
  • Ubuntu Wily 15.10
  • Ubuntu Trusty 14.04 (LTS)
  • Ubuntu Precise 12.04 (LTS)

本頁內容指引你安裝使用由Docker管理的正式包和管理包. 使用這些安裝包能確保你安裝 Docker最新發行包. 若是你想安裝並使用Ubuntu管理提供的軟件包, 參照Ubuntu文檔.css

備註: Ubuntu Utopic 14.10 和 15.04 依舊在 Docker’s APT 倉庫中,但再也不提供官方技術支持.python

前提條件

Docker要求是64位Ubuntu(不管哪一個版本)。另外,內核必須在最小爲3.10。3.10最新版本或更新的版本也行。linux

3.10以前版本缺乏docker運行所須要的特徵一些容器。這些老版本的bug,常常致使數據損失。nginx

使用命令: uname -r 來顯示內核版本:sql

$ uname -r 3.11.0-15-generic 

備註: 若是你以前安裝過Docker 使用的APT, 確保升級你的APT源 到 Docker新版.docker

更新APT

Docker’s APT 倉庫 包括 Docker 1.7.1 及更高版本. 爲了設定 APT 使用最新倉庫的軟件包,:shell

  1. 使用 sudo or root 權限登錄計算機.ubuntu

  2. 打開 terminal window(命令窗口).ruby

  3. 更新安裝包信息, 確保 APT 使用 https 協議, 同時CA 證書已經被安裝.

    $ sudo apt-get update $ sudo apt-get install apt-transport-https ca-certificates 
  4. 添加新的GPGkey.

    $ sudo apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 58118E89F3A912897C070ADBF76221572C52609D 
  5. 用編輯器打開  /etc/apt/sources.list.d/docker.list.

    若是不存在,則新建一個

  6. 刪除任何現有輸入.

  7. 添加與您Ubuntu操做系統相關條目。

    該條目能夠是:

    • On Ubuntu Precise 12.04 (LTS)

      deb https://apt.dockerproject.org/repo ubuntu-precise main 
    • On Ubuntu Trusty 14.04 (LTS)

      deb https://apt.dockerproject.org/repo ubuntu-trusty main 
    • Ubuntu Wily 15.10

      deb https://apt.dockerproject.org/repo ubuntu-wily main 
    • Ubuntu Xenial 16.04 (LTS)

      deb https://apt.dockerproject.org/repo ubuntu-xenial main 

    備註: Docker沒有爲全部架構提供代碼包 .你能夠找到 nightly built binaries in https://master.dockerproject.org. To install docker on a multi-architecture system, add an [arch=...] clause to the entry. 詳細內容參考 Debian Multiarch wiki .

  8. 保存並關閉  /etc/apt/sources.list.d/docker.list file.

  9. 更新APT 軟件包索引.

    $ sudo apt-get update 
  10. 清除舊的repo if it exists.

    $ sudo apt-get purge lxc-docker 
  11. 確保 APT 是從正確的代碼庫拉取下來的.

    $ apt-cache policy docker-engine 

    至此,你能夠 使用命令apt-get upgradeAPT 重新代碼庫拉取代碼.

 Ubuntu 版本相關的先決條件

  • Ubuntu Xenial 16.04 (LTS)
  • Ubuntu Wily 15.10
  • Ubuntu Trusty 14.04 (LTS)

針對Ubuntu Trusty, Wily, and Xenial, 推薦安裝 the linux-image-extra-* 內核包.  linux-image-extra-* 包容許你使用 aufs存儲驅動.

爲了安裝 linux-image-extra-* :

  1. 打開主機命令窗口.

  2. 更新包管理器.

    $ sudo apt-get update 
  3. 安裝推薦包.

    $ sudo apt-get install linux-image-extra-$(uname -r) linux-image-extra-virtual 
  4. 繼續安裝 Docker.

Ubuntu Precise 12.04 (LTS)

針對Ubuntu Precise, Docker 要求是 3.13內核. 若是內核版本早於 3.13, 必須更新. 參考以下表格來對比不一樣包對運行環境的要求:

Package Description
linux-image-generic-lts-trusty Generic Linux kernel image. This kernel has AUFS built in. This is required to run Docker.
linux-headers-generic-lts-trusty Allows packages such as ZFS and VirtualBox guest additions which depend on them. If you didn't install the headers for your existing kernel, then you can skip these headers for the"trusty" kernel. If you're unsure, you should include this package for safety.
xserver-xorg-lts-trusty Optional in non-graphical environments without Unity/Xorg. Required when running Docker on machine with a graphical environment.

To learn more about the reasons for these packages, read the installation instructions for backported kernels, specifically the LTS Enablement Stack — refer to note 5 under each version.
libgl1-mesa-glx-lts-trusty

爲了更新linux內核而且安裝附加包, 經過如下步驟:

  1. 打開主機命令窗口.

  2. 更新包管理器.

    $ sudo apt-get update 
  3. 安裝必需包和可選包

    $ sudo apt-get install linux-image-generic-lts-trusty 

    根據你的運行環境, 你可能須要根據以前提供表格所描述內容安裝其餘內容.

  4. 重啓主機.

    $ sudo reboot
  5. 重啓以後, 繼續安裝Docker.

安裝

確保你已經安裝過你的Ubuntu版本所需前提要求.

而後, 經過如下步驟安裝Docker:

  1. 用具備sudo權限的用戶登錄Ubuntu.

  2. Update your APT package index.

    $ sudo apt-get update 
  3. 安裝 Docker.

    $ sudo apt-get install docker-engine 
  4. 開始使用docker.

    $ sudo service docker start 
  5. 確認docker已被正確安裝.

    $ sudo docker run hello-world 

    這個命令下載一個測試圖片而且在容器(container)中運行. 而後容器container運行, 打印出相關信息.說明安裝成功.

可選配置

下面驅動包含一些可選步驟用來配置Ubuntu環境下Docker.

建立 Docker group

docker 進程(daemon)綁定在 Unix套接字(socket), 而不是TCP端口(port). 因爲Unix默認是 socket權限歸root用戶全部,其餘用戶能夠經過sudo訪問. 由此, docker進程一般使用root用戶運行.

爲了不每次使用docker命令都不得不使用sudo, 建立名爲docker的Unix group並add users to it. 當docker daemon 開始,docker group就會擁有Unix socket 的讀寫權限(read/writable).

警告: The docker group is equivalent to the root用戶; For details on how this impacts security in your system, 查看Docker Daemon Attack Surface 查看細節.

爲了docker group and添加用戶user:

  1. 使用具備sudo權限得用戶登陸Ubuntu.

  2. 建立docker group.

    $ sudo groupadd docker
  3. 添加user到docker group.

    $ sudo usermod -aG docker $USER 
  4. Log out and log back in.

    This ensures your user is running with the correct permissions.

  5. 確認不使用sudo能夠運行docker.

    $ docker run hello-world 

    若是提示失敗信息與下面類似:

    Cannot connect to the Docker daemon. Is 'docker daemon' running on this host? 

    檢查 DOCKER_HOST 環境變量 沒有設置shell. 若是這樣,重置他.

Adjust memory and swap accounting

When users run Docker, they may see these messages when working with an image:

WARNING: Your kernel does not support cgroup swap limit. WARNING: Your kernel does not support swap limit capabilities. Limitation discarded. 

To prevent these messages, enable memory and swap accounting on your system. Enabling memory and swap accounting does induce both a memory overhead and a performance degradation even when Docker is not in use. The memory overhead is about 1% of the total available memory. The performance degradation is roughly 10%.

To enable memory and swap on system using GNU GRUB (GNU GRand Unified Bootloader), do the following:

  1. Log into Ubuntu as a user with sudo privileges.

  2. Edit the /etc/default/grub file.

  3. Set the GRUB_CMDLINE_LINUX value as follows:

    GRUB_CMDLINE_LINUX="cgroup_enable=memory swapaccount=1" 
  4. Save and close the file.

  5. Update GRUB.

    $ sudo update-grub 
  6. Reboot your system.

Enable UFW forwarding

If you use UFW (Uncomplicated Firewall) on the same host as you run Docker, you’ll need to do additional configuration. Docker uses a bridge to manage container networking. By default, UFW drops all forwarding traffic. As a result, for Docker to run when UFW is enabled, you must set UFW’s forwarding policy appropriately.

Also, UFW’s default set of rules denies all incoming traffic. If you want to reach your containers from another host allow incoming connections on the Docker port. The Docker port defaults to 2376 if TLS is enabled or 2375 when it is not. If TLS is not enabled, communication is unencrypted. By default, Docker runs without TLS enabled.

To configure UFW and allow incoming connections on the Docker port:

  1. Log into Ubuntu as a user with sudo privileges.

  2. Verify that UFW is installed and enabled.

    $ sudo ufw status
  3. Open the /etc/default/ufw file for editing.

    $ sudo nano /etc/default/ufw 
  4. Set the DEFAULT_FORWARD_POLICY policy to:

    DEFAULT_FORWARD_POLICY="ACCEPT" 
  5. Save and close the file.

  6. Reload UFW to use the new setting.

    $ sudo ufw reload
  7. Allow incoming connections on the Docker port.

    $ sudo ufw allow 2375/tcp 

Configure a DNS server for use by Docker

Systems that run Ubuntu or an Ubuntu derivative on the desktop typically use127.0.0.1 as the default nameserver in /etc/resolv.conf file. The NetworkManager also sets up dnsmasq to use the real DNS servers of the connection and sets up nameserver 127.0.0.1 in /etc/resolv.conf.

When starting containers on desktop machines with these configurations, Docker users see this warning:

WARNING: Local (127.0.0.1) DNS resolver found in resolv.conf and containers can't use it. Using default external servers : [8.8.8.8 8.8.4.4] 

The warning occurs because Docker containers can’t use the local DNS nameserver. Instead, Docker defaults to using an external nameserver.

To avoid this warning, you can specify a DNS server for use by Docker containers. Or, you can disable dnsmasq in NetworkManager. Though, disablingdnsmasq might make DNS resolution slower on some networks.

The instructions below describe how to configure the Docker daemon running on Ubuntu 14.10 or below. Ubuntu 15.04 and above use systemd as the boot and service manager. Refer to control and configure Docker with systemd to configure a daemon controlled by systemd.

To specify a DNS server for use by Docker:

  1. Log into Ubuntu as a user with sudo privileges.

  2. Open the /etc/default/docker file for editing.

    $ sudo nano /etc/default/docker 
  3. Add a setting for Docker.

    DOCKER_OPTS="--dns 8.8.8.8" 

    Replace 8.8.8.8 with a local DNS server such as 192.168.1.1. You can also specify multiple DNS servers. Separated them with spaces, for example:

    --dns 8.8.8.8 --dns 192.168.1.1 

    Warning: If you’re doing this on a laptop which connects to various networks, make sure to choose a public DNS server.

  4. Save and close the file.

  5. Restart the Docker daemon.

    $ sudo service docker restart

   

Or, as an alternative to the previous procedure, disable dnsmasq in NetworkManager (this might slow your network).

  1. Open the /etc/NetworkManager/NetworkManager.conf file for editing.

    $ sudo nano /etc/NetworkManager/NetworkManager.conf
  2. Comment out the dns=dnsmasq line:

    dns=dnsmasq 
  3. 保存並關閉.

  4. 重啓NetworkManager 和 Docker.

    $ sudo restart network-manager $ sudo restart docker

Configure Docker to start on boot

Ubuntu uses systemd as its boot and service manager 15.04 onwards andupstart for versions 14.10 and below.

For 15.04 and up, to configure the docker daemon to start on boot, run

$ sudo systemctl enable docker 

For 14.10 and below the above installation method automatically configuresupstart to start the docker daemon on boot

更新Docker

使用apt-get來安裝Docker最新版:

$ sudo apt-get upgrade docker-engine

卸載

卸載Docker包:

$ sudo apt-get purge docker-engine 

卸載Docker包及依賴:

$ sudo apt-get autoremove --purge docker-engine 

上面命令會刪除images, containers, volumes, user created configuration files on your host. If you wish to delete all images, containers, and volumes run the following command:

$ rm -rf /var/lib/docker 

You must delete the user created configuration files manually.

相關文章
相關標籤/搜索