docker官网（docker官网下载安装）

本篇文章给大家谈谈docker官网，以及docker官网下载安装对应的知识点，希望对各位有所帮助，不要忘了收藏本站喔。

本文目录一览：

• 1、安装Docker-解决官网下载特别慢的问题
• 2、Docker 概述
• 3、DooD:Docker+Jenkins
• 4、CentOS8.1安装docker
• 5、Docker 找不到/etc/docker/daemon.json问题解决
• 6、docker与docker-compose介绍，对比与使用

安装Docker-解决官网下载特别慢的问题

1. 安装／升级Docker客户端

对于10.10.3以下的用户 推荐使用Docker Toolbox

Mac安装文件：

对于10.10.3以上的用户 推荐使用Docker for Mac

Mac安装文件：

2. 配置镜像加速器

针对安装了Docker Toolbox的用户，您可以参考以下配置步骤：

创建一台安装有Docker环境的Linux虚拟机，指定机器名称宏散稿为default，同时配置Docker加速器地址。

docker-machine create --engine-registry-mirror= -d virtualbox default

查看机器的环境配置，并配置到本地，并通过Docker客户端访问Docker服务。

docker-machine env defaulteval "$(docker-machine env default)"docker info

针对安装了Docker for Mac的掘乎用户，您可以参考以下配置步骤：

右键点击桌面顶栏的 docker 图标，选择 Preferences ，在 Daemon 标签（Docker 17.03 之前版本为 Advanced 标签）下的 Registry mirrors 列表中将蔽孝

加到"registry-mirrors"的数组里，点击 Apply Restart按钮，等待Docker重启并应用配置的镜像加速器。

[img]

Docker 概述

本文翻译自docker官网：

Docker is an open platform for developing, shipping, and running applications.

Docker enables you to separate your applications from your infrastructure so

you can deliver software quickly. With Docker, you can manage your infrastructure

in the same ways you manage your applications. By taking advantage of Docker's

methodologies for shipping, testing, and deploying code quickly, you can

significantly reduce the delay between writing code and running it in production.

Docker provides the ability to package and run an application in a loosely isolated

environment called a container. The isolation and security allow you to run many

containers simultaneously on a given host. Containers are lightweight and contain

everything needed to run the application, so you do not need to rely on what is

currently installed on the host. You can easily share containers while you work,

and be sure that everyone you share with gets the same container that works in the

same way.

Docker provides tooling and a platform to manage the lifecycle of your containers:

Fast, consistent delivery of your applications

Docker streamlines the development lifecycle by allowing developers to work in

standardized environments using local containers which provide your applications

and services. Containers are great for continuous integration and continuous

delivery (CI/CD) workflows.

Consider the following example scenario:

Responsive deployment and scaling

Docker's container-based platform allows for highly portable workloads. Docker

containers can run on a developer's local laptop, on physical or virtual

machines in a data center, on cloud providers, or in a mixture of environments.

Docker's portability and lightweight nature also make it easy to dynamically

manage workloads, scaling up or tearing down applications and services as

business needs dictate, in near real time.

Running more workloads on the same hardware

Docker is lightweight and fast. It provides a viable, cost-effective alternative

to hypervisor-based virtual machines, so you can use more of your compute

capacity to achieve your business goals. Docker is perfect for high density

environments and for small and medium deployments where you need to do more with

fewer resources.

Docker uses a client-server architecture. The Docker client talks to the

Docker daemon , which does the heavy lifting of building, running, and

distributing your Docker containers. The Docker client and daemon can

run on the same system, or you can connect a Docker client to a remote Docker

daemon. The Docker client and daemon communicate using a REST API, over UNIX

sockets or a network interface. Another Docker client is Docker Compose,

that lets you work with applications consisting of a set of containers.

[图片上传失败...(image-17b2f-1618407573391)]

The Docker daemon ( dockerd ) listens for Docker API requests and manages Docker

objects such as images, containers, networks, and volumes. A daemon can also

communicate with other daemons to manage Docker services.

The Docker client ( docker ) is the primary way that many Docker users interact

with Docker. When you use commands such as docker run , the client sends these

commands to dockerd , which carries them out. The docker command uses the

Docker API. The Docker client can communicate with more than one daemon.

A Docker registry stores Docker images. Docker Hub is a public

registry that anyone can use, and Docker is configured to look for images on

Docker Hub by default. You can even run your own private registry.

When you use the docker pull or docker run commands, the required images are

pulled from your configured registry. When you use the docker push command,

your image is pushed to your configured registry.

When you use Docker, you are creating and using images, containers, networks,

volumes, plugins, and other objects. This section is a brief overview of some

of those objects.

An image is a read-only template with instructions for creating a Docker

container. Often, an image is based on another image, with some additional

customization. For example, you may build an image which is based on the ubuntu

image, but installs the Apache web server and your application, as well as the

configuration details needed to make your application run.

You might create your own images or you might only use those created by others

and published in a registry. To build your own image, you create a Dockerfile

with a simple syntax for defining the steps needed to create the image and run

it. Each instruction in a Dockerfile creates a layer in the image. When you

change the Dockerfile and rebuild the image, only those layers which have

changed are rebuilt. This is part of what makes images so lightweight, small,

and fast, when compared to other virtualization technologies.

A container is a runnable instance of an image. You can create, start, stop,

move, or delete a container using the Docker API or CLI. You can connect a

container to one or more networks, attach storage to it, or even create a new

image based on its current state.

By default, a container is relatively well isolated from other containers and

its host machine. You can control how isolated a container's network, storage,

or other underlying subsystems are from other containers or from the host

machine.

A container is defined by its image as well as any configuration options you

provide to it when you create or start it. When a container is removed, any changes to

its state that are not stored in persistent storage disappear.

The following command runs an ubuntu container, attaches interactively to your

local command-line session, and runs /bin/bash .

When you run this command, the following happens (assuming you are using

the default registry configuration):

Docker is written in the Go programming language and takes

advantage of several features of the Linux kernel to deliver its functionality.

Docker uses a technology called namespaces to provide the isolated workspace

called the container . When you run a container, Docker creates a set of

namespaces for that container.

These namespaces provide a layer of isolation. Each aspect of a container runs

in a separate namespace and its access is limited to that namespace.

DooD:Docker+Jenkins

第一次发布博客。希望可以给需要的朋友们一些帮助。

本文基于64位的CentOS 7.2系统，内核版本如下：

Docker版本如下：

如需安装Docker，请点击： 安装Docker

如需安装Docker加速器，请点击： 配置Docker加速器

其实就是运行一个Jenkins镜像的docker容器，这种方式使用socket套接字（一般默认是/var/run/docker.sock文件）和宿主机进行交互，只限于本地通信。不会去监听任何端口。在创建Jenkins镜像时，可以给jenkins用户赋予sudo权限来调用docker命令；或者将jenkins用户加入到docker组，就可以直接在容器中调闭裤用docker命令，下文会分别讲到两种情况的Dockerfile的写法。不过相比较于不同的宿主机docker组的不同，使用腔态明sudo更具有普适性和可移植性。

顾名思义，就是在Docker容器中重新安装一个Docker应用。容器中安装Docker和宿主机安装的Docker是完全没有关联的两个程序。一般情况下，我们想要的只是一个运行于docker的CI/CD环境，我们需要容器内外只有一个docker engine。 DinD显然比我们想要的要复杂的多，而且可能还有一些意想不到的问题会出现。

更详细的了解，请参考下面两篇文章：

Docker还可以对外暴露Remote API，通过http/https就可以与docker engine进行通信，因为打开Remote API相应的要对外暴露端口，所以相对来说是不安全的。

在Jenkins容器中可以通过配置相应的Docker plugin，并在“系统管理”——“系统设置”——“云”中增添响应的Remote API信息。

详细信息请参考：

进过对比，我使用的是第一种方式：DooD。

注意点：请确保宿主机的doeker server已经开启本地套接字访问和远程通信

默认情况下，Docker守护进程会生成一个socket（/var/run/docker.sock）文件来进行本地进程通信，而不会监听任何端口，因此只能在本地使用docker客户端或者使用Docker API进行操作。

如果想在其他主机上操作Docker主机，就需要让Docker守护进程监听一个端口，这样才能实现远程通信。

目前开启本地套接字访问和远程通信有以下两种方式：

把以下内容添加进json文件中，注意添加前请确认2375端口是否被占用！！伍告！

如下图所示：

以上两种方式都可以通过下面的方式验证 docker remote API的2375端口是否开启

netstat -apn | grep 2375

在本地宿主机上新建一个Jenkins镜像数据的挂载目录，进行Jenkins数据的备份和持久化；因为Jenkins镜像中的Dockerfile中/var/jenkins_home权限为1000:1000，所以此处我们需要修改宿主机上的挂载目录权限，否则会出现权限不足的问题。注意：如果在生产中这样使用，一开始需要给/var/jenkins分配一个合理的容量，否则随着jenkins构建的增多会出现空间不足等问题。如下图：

第一种：在docker容器中，jenkins用户使用sudo执行docker命令

第二种：在docker容器中，jenkins用户可直接使用docker命令

我选用的是第二种，但是因为所在宿主机的不同，docker_gid会有所差异，建议使用第一种方式。

在上一步构建好的Dockerfile所在目录，执行下面的命令构建Jenkins镜像

使用上一步构建好的镜像，启动Jenkins容器，命令如下

使用如下命令查看安装密码，也可直接去看容器里边对应位置的文件（/var/jenkins_home/secrets/initialAdminPassword），或者去宿主机挂载的目录下查看文件（/var/jenkins//secrets/initialAdminPassword）

5.1 docker-client版本问题

Q1:搭建的jenkins容器出现下列错误，在容器中无法正常运行docker命令，可能是docker client的版本问题。

我当时出现问题的版本如下：

A1:该问题，有两种解决办法：第一，卸载重新安装合适的版本，上图这个版本是我使用yum install 安装的版本；第二种，只需安装docker-client。

Docker官网：

Docker社区：

DaoCloud：

DockOne:

Jenkins Base Dockerfile Github:

CentOS8.1安装docker

Docker官网地址：

Docker软件镜像查询地址：

国内镜像站：阿乎丛里云

如果使用超级管理员登录，不需要在命令前加sudo

1.安装必要的一些系统工具

2.添加软件源信息(由于国内使用官网的太慢了，这里使用阿里的资源库来加速)

3.更新 yum 缓闹含存

4.更新并安装 Docker-CEsudo

5.查看安装版本

6.开启Docker服务

执行sudo yum -y install docker-ce安装docker命令时出错，液顷笑提示：containerd.io版本过低。具体如下：

解决方法：单独安装 containerd.io

之后重新安装docker

安装时出现下面的错误

Error: transaction check vs depsolve:rpmlib(PayloadIsZstd) = 5.4.18-1is needed by containerd.io-1.2.10-3.2.fc31.x86_64To diagnose the problem, try running: 'rpm -Va --nofiles --nodigest'.You probably have corrupted RPMDB, running 'rpm --rebuilddb' might fix the issue.

这个是一般是版本依赖冲突，或者版本过高的问题，换为1.2.6-3.3版本即可

Docker 找不到/etc/docker/daemon.json问题解决

总所周知的原因，中国直接访问dockerhub会非常的慢，所以需要配置镜像加速。

在配置dock镜像加速的时候需要把加速阿乱慧里的加速写入daemon.json文件。

但是奇怪的是别说daemon.json文件哗弊答了，在etc目录下，我连docker目录都找不到。

于是访问官网： docker官网配置deamon

看到下面一句话：

To configure the Docker daemon using a JSON file, create a file at/卜陆etc/docker/daemon.jsonon Linux systems, orC:\ProgramData\docker\config\daemon.jsonon Windows. On MacOS go to the whale in the taskbar Preferences Daemon Advanced.

然后写入加速配置：

{

"registry-mirrors": [""]

}

出现这句或者类似表明加速器配置成功

docker与docker-compose介绍，对比与使用

docker是一个供开发和运维人员开发，测试，部署和运行应用的容器平台。这种用linux container部署应用的方式耐巧叫容器化。

compose是一个用于运行和管理多个容手亩灶器化应用的工具毕扮。

我们可以列出下列几项来进行二者对比：

1.docker是自动化构建镜像，并启动镜像。 docker compose是自动化编排容器。

2. docker是基于Dockerfile得到images,启动的时候是一个单独的container

3. docker-compose是基于docker-compose.yml,通常启动的时候是一个服务，这个服务通常由多个container共同组成，并且端口，配置等由docker-compose定义好。

4.两者都需要安装，但是要使用docker-compose，必须已经安装docker

接下来，我们来安装docker ce，docker-compose，然后根据官网的关于docker-compose一个简单的例子来进一步理解

安装docker ce:

安装docker-compose:

或者获取安装脚本进行安装（仅限于centos7 or rhel7）

docker-compose例子官网URL:

文件目录

从docker-compose.yml我们可以看到，这个python应用包含两个部分，一个部分是web service, 一个是redis service,我们用‘docker-compose up’ 去build images or pull images, create containers和run这些containers。

最终，我们看到这个service在运行。其背后有4个images, 2个containers.而通过docke-compose则可以直接操作这整个service。

关于docker官网和docker官网下载安装的介绍到此就结束了，不知道你从中找到你需要的信息了吗 ？如果你还想了解更多这方面的信息，记得收藏关注本站。