Docker 专用术语

This section lists terms and definitions you should be familiar with before getting deeper into Docker. For further definitions, see the extensiveglossary provided by Docker .

Container image: A package with all the dependencies and information needed to create a container. An image includes all the dependencies (such as frameworks) plus deployment and execution configuration to be used by a container runtime. Usually, an image derives from multiple base images that are layers stacked on top of each other to form the container’s filesystem. An image is immutable once it has been created.

Container: An instance of a Docker image. A container represents the execution of a single application, process, or service. It consists of the contents of a Docker image, an execution environment, and a standard set of instructions. When scaling a service, you create multiple instances of a container from the same image. Or a batch job can create multiple containers from the same image, passing different parameters to each instance.

Tag: A mark or label you can apply to images so that different images or versions of the same image (depending on the version number or the target environment) can be identified.

Dockerfile: A text file that contains instructions for how to build a Docker image.

Build: The action of building a container image based on the information and context provided by its Dockerfile, plus additional files in the folder where the image is built. You can build images with the Docker docker build command.

Repository (repo): A collection of related Docker images, labeled with a tag that indicates the image version. Some repos contain multiple variants of a specific image, such as an image containing SDKs (heavier), an image containing only runtimes (lighter), etc. Those variants can be marked with tags. A single repo can contain platform variants, such as a Linux image and a Windows image.

Registry: A service that provides access to repositories. The default registry for most public images is Docker Hub (owned by Docker as an organization). A registry usually contains repositories from multiple teams. Companies often have private registries to store and manage images they’ve created. Azure Container Registry is another example.

Docker Hub: A public registry to upload images and work with them. Docker Hub provides Docker image hosting, public or private registries, build triggers and web hooks, and integration with GitHub and Bitbucket.

Azure Container Registry: A public resource for working with Docker images and its components in Azure. This provides a registry that is close to your deployments in Azure and that gives you control over access, making it possible to use your Azure Active Directory groups and permissions.

Docker Trusted Registry (DTR): A Docker registry service (from Docker) that can be installed on-premises so it lives within the organization’s datacenter and network. It is convenient for private images that should be managed within the enterprise. Docker Trusted Registry is included as part of the Docker Datacenter product. For more information, see Docker Trusted Registry (DTR).

Docker Community Edition (CE): Development tools for Windows and macOS for building, running, and testing containers locally. Docker CE for Windows provides development environments for both Linux and Windows Containers. The Linux Docker host on Windows is based on a Hyper-Vvirtual machine. The host for Windows Containers is directly based on Windows. Docker CE for Mac is based on the Apple Hypervisor framework and the xhyve hypervisor, which provides a Linux Docker host virtual machine on Mac OS X. Docker CE for Windows and for Mac replaces Docker Toolbox, which was based on Oracle VirtualBox.

Docker Enterprise Edition (EE): An enterprise-scale version of Docker tools for Linux and Windows development.

Compose: A command-line tool and YAML file format with metadata for defining and running multi-container applications. You define a single application based on multiple images with one or more .yml files that can override values depending on the environment. After you have created the definitions, you can deploy the whole multi-container application with a single command (docker-compose up) that creates a container per image on the Docker host.

Cluster: A collection of Docker hosts exposed as if it were a single virtual Docker host, so that the application can scale to multiple instances of the services spread across multiple hosts within the cluster. Docker clusters can be created with Docker Swarm, Mesosphere DC/OS, Kubernetes, and Azure Service Fabric. (If you use Docker Swarm for managing a cluster, you typically refer to the cluster as a swarm instead of a cluster.)

Orchestrator: A tool that simplifies management of clusters and Docker hosts. Orchestrators enable you to manage their images, containers, and hosts through a command line interface (CLI) or a graphical UI. You can manage container networking, configurations, load balancing, service discovery, high availability, Docker host configuration, and more. An orchestrator is responsible for running, distributing, scaling, and healing workloads across a collection of nodes. Typically, orchestrator products are the same products that provide cluster infrastructure, like Mesosphere DC/OS, Kubernetes, Docker Swarm, and Azure Service Fabric.

时间: 2024-10-05 16:02:01

Docker 专用术语的相关文章

Docker基本术语

本文介绍Docker最基本也是最重要的一些基本术语: 镜像(image):镜像是构建docker世界的基石,用户基于镜像创建容器,它是基于联合文件系统的一种层式结构,由一系列指令一步步构建出来的.可以简单的理解为镜像就是容器运行的程序代码. Registry:Docker用Registry来保存用户构建的镜像.Registry分为公共和私有两种.Docker公司运营的公共Registry叫做Docker Hub.用户可以在Docker Hub上注册账号,分享并保存自己构建的镜像. 容器(cont

docker常用术语命令

镜像(Image) vs Dockerfile 这组概念很少会让人产生疑惑,但是这两者的区别非常重要.Docker在镜像(image)中运行你的代码,而不是Dockerfile.Dockerfile是通过docker build命令来编译镜像的配置文件. 如果你去浏览一下public index的话,你将会看到那里罗列了很多镜像文件.但是,也许有些奇怪的是,你将看不到任何编译出它们的dockerfile.镜像文件就是从Dockerfile编译而得到的不透明资产(opaque asset ). 当

容器与Docker简介(三)Docker相关术语——微软微服务电子书翻译系列

本节列出了在更加深入Docker之前应该熟悉的术语和定义. 有关详细的定义,请参阅Docker提供的术语表. 容器镜像(Container image):具有创建容器所需要的所有依赖和信息的包. 镜像包括所有依赖(如框架)以及容器运行时使用的部署方式和执行配置. 通常,一个镜像来自于多个基本镜像,这些镜像堆叠于彼此之上,以形成容器的文件系统. 镜像创建后将不可改变. 容器(Container):Docker镜像的一个实例. 容器表示单个应用程序,进程或服务的运行. 它由Docker镜像,执行环境

试讲DOCKER专用

内容概要: DOCKER简介 为什么要用DOCKER DOCKER的应用场景 DOCKER基础 一 DOCKER简介 Docker是Docker.Inc公司开源的一个基于轻量级虚拟化技术的容器引擎项目,整个项目基于Go语言开发,并遵从Apache 2.0协议.通过分层镜像标准化和内核虚拟化技术,Docker使得应用开发者和运维工程师能够以统一的方式跨平台地发布应用,并且在几乎没有额外开销的情况下提供资源隔离的应用运行环境.由于众多新颖的特性以及项目本身的开放性,Docker在不到两年的时间里迅速

android audio开发的一些专用术语(待翻译)

Audio Terminology IN THIS DOCUMENT Generic Terms Digital Audio Hardware and Accessories Audio Signal Path Android-Specific Terms Sample Rate Conversion This document provides a glossary of audio-related terminology, including a list of widely used, g

无需安装 vsftpd , 直接使用 FTP 来管理 docker 容器中的文件

无图无真相,先放个效果图: 背景 使用 docker 来跑一些服务很方便,但是有的时候想管理容器里面的文件却很麻烦 -- 一般常规做法有3种: 通过数据卷或数据卷容器的方式 启动容器的时候时候启动 vsftpd 或者 sshd 等服务,并开启端口映射,然后通过 ftp/sftp 连上去管理 进入容器的终端,通过命令行管理 但是这些做法都有一定的缺陷和不便: 1和2都是需要在启动容器的时候做一些配置,如果容器已经启动了就歇菜了.而且2需要额外的端口映射,占用主机的端口.3的做法比较 geek ,而

Docker 字典

File System为了让Linux运行起来,通常需要2个file system boot file system (bootfs) root file system (rootfs) 在传统的Linux boot, kernel首先mount(挂载)rootfs, 此时为read-only模式, 然后检查integrity(完整性), 接着切换整个rootfs为read-write模式 Docker与传统的Linux有些不同, 一样mount(挂载)rootfs, 也是进入read-only

一些常用术语

1.打表 打表,是一个信息学专用术语,意指对某种找规律等题目,直接输出答案.这种算法也在对某种题目没有最优解法时,用来得到分数的一种策略. 打表一般分为两步:找到答案与输出答案. 找到答案的方式 一.通过找规律,找出对于每个输入数据n,f[n]的最终结果. 常见题目有费波纳契数列等: 二.通过暴力搜索,找出对于数据的答案,适用于数据较大,题目简单的情况: 三.通过手算,找出每个数据的答案,适用于数据较小且题目较难的情况. 输出答案的方式 一.直接把打表程序加上输入输出提交:耗时大,程序占用空间小

Windows Docker和Windows Nano Server来啦!

今天盆盆起了一个大早,6点不到就醒了,打开邮箱一看,好家伙,被Windows Docker的大新闻给刷屏了! 首先先来说说看Nano Server. 何为Nano Server? 盆盆的理解,就是专门为Windows Azure和Docker而生的Cloud OS!从开发者的角度来看,Docker其实是一种类似于PaaS的技术,对外展示的是打包好的应用,而不像传统的虚拟化那样需要对操作系统进行维护. 对于Docker而言,所有的容器都是共享内核的,这个内核自然越小越好.对于Linux而言,大家都