亚洲国产日韩欧美一区二区三区,精品亚洲国产成人av在线,国产99视频精品免视看7,99国产精品久久久久久久成人热,欧美日韩亚洲国产综合乱

directory search
Compose About versions and upgrading (Compose) ASP.NET Core + SQL Server on Linux (Compose) CLI environment variables (Compose) Command-line completion (Compose) Compose(組成) Compose command-line reference(組合命令行參考) Control startup order (Compose) Django and PostgreSQL (Compose) Docker stacks and distributed application bundles (Compose) docker-compose build(docker-compose構(gòu)建) docker-compose bundle docker-compose config docker-compose create docker-compose down docker-compose events docker-compose exec docker-compose help docker-compose images docker-compose kill docker-compose logs docker-compose pause docker-compose port docker-compose ps docker-compose pull docker-compose push docker-compose restart docker-compose rm docker-compose run docker-compose scale docker-compose start docker-compose stop docker-compose top docker-compose unpause docker-compose up Environment file (Compose) Environment variables in Compose Extend services in Compose Frequently asked questions (Compose) Getting started (Compose) Install Compose Link environment variables (deprecated) (Compose) Networking in Compose Overview of Docker Compose Overview of docker-compose CLI Quickstart: Compose and WordPress Rails and PostgreSQL (Compose) Sample apps with Compose Using Compose in production Using Compose with Swarm Engine .NET Core application (Engine) About images, containers, and storage drivers (Engine) Add nodes to the swarm (Engine) Apply custom metadata (Engine) Apply rolling updates (Engine) apt-cacher-ng Best practices for writing Dockerfiles (Engine) Binaries (Engine) Bind container ports to the host (Engine) Breaking changes (Engine) Build your own bridge (Engine) Configure container DNS (Engine) Configure container DNS in user-defined networks (Engine) CouchDB (Engine) Create a base image (Engine) Create a swarm (Engine) Customize the docker0 bridge (Engine) Debian (Engine) Default bridge network Delete the service (Engine) Deploy a service (Engine) Deploy services to a swarm (Engine) Deprecated Engine features Docker container networking (Engine) Docker overview (Engine) Docker run reference (Engine) Dockerfile reference (Engine) Dockerize an application Drain a node (Engine) Engine FAQ (Engine) Fedora (Engine) Get started (Engine) Get started with macvlan network driver (Engine) Get started with multi-host networking (Engine) How nodes work (Engine) How services work (Engine) Image management (Engine) Inspect the service (Engine) Install Docker (Engine) IPv6 with Docker (Engine) Join nodes to a swarm (Engine) Legacy container links (Engine) Lock your swarm (Engine) Manage nodes in a swarm (Engine) Manage sensitive data with Docker secrets (Engine) Manage swarm security with PKI (Engine) Manage swarm service networks (Engine) Migrate to Engine 1.10 Optional Linux post-installation steps (Engine) Overview (Engine) PostgreSQL (Engine) Raft consensus in swarm mode (Engine) Riak (Engine) Run Docker Engine in swarm mode Scale the service (Engine) SDKs (Engine) Select a storage driver (Engine) Set up for the tutorial (Engine) SSHd (Engine) Storage driver overview (Engine) Store service configuration data (Engine) Swarm administration guide (Engine) Swarm mode key concepts (Engine) Swarm mode overlay network security model (Engine) Swarm mode overview (Engine) Understand container communication (Engine) Use multi-stage builds (Engine) Use swarm mode routing mesh (Engine) Use the AUFS storage driver (Engine) Use the Btrfs storage driver (Engine) Use the Device mapper storage driver (Engine) Use the OverlayFS storage driver (Engine) Use the VFS storage driver (Engine) Use the ZFS storage driver (Engine) Engine: Admin Guide Amazon CloudWatch logs logging driver (Engine) Bind mounts (Engine) Collect Docker metrics with Prometheus (Engine) Configuring and running Docker (Engine) Configuring logging drivers (Engine) Control and configure Docker with systemd (Engine) ETW logging driver (Engine) Fluentd logging driver (Engine) Format command and log output (Engine) Google Cloud logging driver (Engine) Graylog Extended Format (GELF) logging driver (Engine) Journald logging driver (Engine) JSON File logging driver (Engine) Keep containers alive during daemon downtime (Engine) Limit a container's resources (Engine) Link via an ambassador container (Engine) Log tags for logging driver (Engine) Logentries logging driver (Engine) PowerShell DSC usage (Engine) Prune unused Docker objects (Engine) Run multiple services in a container (Engine) Runtime metrics (Engine) Splunk logging driver (Engine) Start containers automatically (Engine) Storage overview (Engine) Syslog logging driver (Engine) tmpfs mounts Troubleshoot volume problems (Engine) Use a logging driver plugin (Engine) Using Ansible (Engine) Using Chef (Engine) Using Puppet (Engine) View a container's logs (Engine) Volumes (Engine) Engine: CLI Daemon CLI reference (dockerd) (Engine) docker docker attach docker build docker checkpoint docker checkpoint create docker checkpoint ls docker checkpoint rm docker commit docker config docker config create docker config inspect docker config ls docker config rm docker container docker container attach docker container commit docker container cp docker container create docker container diff docker container exec docker container export docker container inspect docker container kill docker container logs docker container ls docker container pause docker container port docker container prune docker container rename docker container restart docker container rm docker container run docker container start docker container stats docker container stop docker container top docker container unpause docker container update docker container wait docker cp docker create docker deploy docker diff docker events docker exec docker export docker history docker image docker image build docker image history docker image import docker image inspect docker image load docker image ls docker image prune docker image pull docker image push docker image rm docker image save docker image tag docker images docker import docker info docker inspect docker kill docker load docker login docker logout docker logs docker network docker network connect docker network create docker network disconnect docker network inspect docker network ls docker network prune docker network rm docker node docker node demote docker node inspect docker node ls docker node promote docker node ps docker node rm docker node update docker pause docker plugin docker plugin create docker plugin disable docker plugin enable docker plugin inspect docker plugin install docker plugin ls docker plugin push docker plugin rm docker plugin set docker plugin upgrade docker port docker ps docker pull docker push docker rename docker restart docker rm docker rmi docker run docker save docker search docker secret docker secret create docker secret inspect docker secret ls docker secret rm docker service docker service create docker service inspect docker service logs docker service ls docker service ps docker service rm docker service scale docker service update docker stack docker stack deploy docker stack ls docker stack ps docker stack rm docker stack services docker start docker stats docker stop docker swarm docker swarm ca docker swarm init docker swarm join docker swarm join-token docker swarm leave docker swarm unlock docker swarm unlock-key docker swarm update docker system docker system df docker system events docker system info docker system prune docker tag docker top docker unpause docker update docker version docker volume docker volume create docker volume inspect docker volume ls docker volume prune docker volume rm docker wait Use the Docker command line (Engine) Engine: Extend Access authorization plugin (Engine) Docker log driver plugins Docker network driver plugins (Engine) Extending Engine with plugins Managed plugin system (Engine) Plugin configuration (Engine) Plugins API (Engine) Volume plugins (Engine) Engine: Security AppArmor security profiles for Docker (Engine) Automation with content trust (Engine) Content trust in Docker (Engine) Delegations for content trust (Engine) Deploying Notary (Engine) Docker security (Engine) Docker security non-events (Engine) Isolate containers with a user namespace (Engine) Manage keys for content trust (Engine) Play in a content trust sandbox (Engine) Protect the Docker daemon socket (Engine) Seccomp security profiles for Docker (Engine) Secure Engine Use trusted images Using certificates for repository client verification (Engine) Engine: Tutorials Engine tutorials Network containers (Engine) Get Started Part 1: Orientation Part 2: Containers Part 3: Services Part 4: Swarms Part 5: Stacks Part 6: Deploy your app Machine Amazon Web Services (Machine) Digital Ocean (Machine) docker-machine active docker-machine config docker-machine create docker-machine env docker-machine help docker-machine inspect docker-machine ip docker-machine kill docker-machine ls docker-machine provision docker-machine regenerate-certs docker-machine restart docker-machine rm docker-machine scp docker-machine ssh docker-machine start docker-machine status docker-machine stop docker-machine upgrade docker-machine url Driver options and operating system defaults (Machine) Drivers overview (Machine) Exoscale (Machine) Generic (Machine) Get started with a local VM (Machine) Google Compute Engine (Machine) IBM Softlayer (Machine) Install Machine Machine Machine CLI overview Machine command-line completion Machine concepts and help Machine overview Microsoft Azure (Machine) Microsoft Hyper-V (Machine) Migrate from Boot2Docker to Machine OpenStack (Machine) Oracle VirtualBox (Machine) Provision AWS EC2 instances (Machine) Provision Digital Ocean Droplets (Machine) Provision hosts in the cloud (Machine) Rackspace (Machine) VMware Fusion (Machine) VMware vCloud Air (Machine) VMware vSphere (Machine) Notary Client configuration (Notary) Common Server and signer configurations (Notary) Getting started with Notary Notary changelog Notary configuration files Running a Notary service Server configuration (Notary) Signer configuration (Notary) Understand the service architecture (Notary) Use the Notary client
characters

創(chuàng)建一臺(tái)機(jī)器。需要該--driver標(biāo)志來(lái)指示應(yīng)在哪個(gè)提供商(VirtualBox,DigitalOcean,AWS等)上創(chuàng)建機(jī)器,以及用于指示所創(chuàng)建機(jī)器的名稱的參數(shù)。

$ docker-machine create --driver virtualbox dev
Creating CA: /home/username/.docker/machine/certs/ca.pem
Creating client certificate: /home/username/.docker/machine/certs/cert.pem
Image cache does not exist, creating it at /home/username/.docker/machine/cache...
No default boot2docker iso found locally, downloading the latest release...
Downloading https://github.com/boot2docker/boot2docker/releases/download/v1.6.2/boot2docker.
iso to /home/username/.docker/machine/cache/boot2docker.iso...
Creating VirtualBox VM...
Creating SSH key...
Starting VirtualBox VM...
Starting VM...To see how to connect Docker to this machine, run: docker-machine env dev

訪問(wèn)幫助文本中特定于驅(qū)動(dòng)程序的標(biāo)志。

docker-machine create命令有一些適用于所有驅(qū)動(dòng)程序的標(biāo)志。這些主要控制用戶可能希望定制的機(jī)器供應(yīng)過(guò)程(包括創(chuàng)建Docker Swarm容器)的各個(gè)方面。

$ docker-machine create
Docker Machine Version: 0.5.0 (45e3688)Usage: docker-machine create [OPTIONS] [arg...]Create a machine.Run 'docker-machine create --driver name' to include the create flags for that driver in the help text.Options:   --driver, -d "none"                                                                                  Driver to create machine with.   --engine-install-url "https://get.docker.com"                                                        Custom URL to use for engine installation [$MACHINE_DOCKER_INSTALL_URL]   --engine-opt [--engine-opt option --engine-opt option]                                               Specify arbitrary flags to include with the created engine in the form flag=value   --engine-insecure-registry [--engine-insecure-registry option --engine-insecure-registry option]     Specify insecure registries to allow with the created engine   --engine-registry-mirror [--engine-registry-mirror option --engine-registry-mirror option]           Specify registry mirrors to use [$ENGINE_REGISTRY_MIRROR]   --engine-label [--engine-label option --engine-label option]                                         Specify labels for the created engine   --engine-storage-driver                                                                              Specify a storage driver to use with the engine   --engine-env [--engine-env option --engine-env option]                                               Specify environment variables to set in the engine   --swarm                                                                                              Configure Machine with Swarm   --swarm-image "swarm:latest"                                                                         Specify Docker image to use for Swarm [$MACHINE_SWARM_IMAGE]   --swarm-master                                                                                       Configure Machine to be a Swarm master   --swarm-discovery                                                                                    Discovery service to use with Swarm   --swarm-strategy "spread"                                                                            Define a default scheduling strategy for Swarm   --swarm-opt [--swarm-opt option --swarm-opt option]                                                  Define arbitrary flags for swarm   --swarm-host "tcp://0.0.0.0:3376"                                                                    ip/socket to listen on for Swarm master   --swarm-addr                                                                                         addr to advertise for Swarm (default: detect and use the machine IP)   --swarm-experimental                                                                                 Enable Swarm experimental features

此外,驅(qū)動(dòng)程序可以指定機(jī)器可以接受的標(biāo)志作為其插件代碼的一部分。這些允許用戶自定義創(chuàng)建的機(jī)器的特定于提供者的參數(shù),例如size(--amazonec2-instance-type m1.medium),地理區(qū)域(--amazonec2-region us-west-1)等。

若要查看特定于提供程序的標(biāo)志,只需傳遞--driver調(diào)用create幫助短信。

$ docker-machine create --driver virtualbox --help
Usage: docker-machine create [OPTIONS] [arg...]
Create a machine.Run 'docker-machine create --driver name' to include the create flags for that driver in the help text.Options:   --driver, -d "none"                                                                                  Driver to create machine with.   --engine-env [--engine-env option --engine-env option]                                               Specify environment variables to set in the engine   --engine-insecure-registry [--engine-insecure-registry option --engine-insecure-registry option]     Specify insecure registries to allow with the created engine   --engine-install-url "https://get.docker.com"                                                        Custom URL to use for engine installation [$MACHINE_DOCKER_INSTALL_URL]   --engine-label [--engine-label option --engine-label option]                                         Specify labels for the created engine   --engine-opt [--engine-opt option --engine-opt option]                                               Specify arbitrary flags to include with the created engine in the form flag=value   --engine-registry-mirror [--engine-registry-mirror option --engine-registry-mirror option]           Specify registry mirrors to use [$ENGINE_REGISTRY_MIRROR]   --engine-storage-driver                                                                              Specify a storage driver to use with the engine   --swarm                                                                                              Configure Machine with Swarm   --swarm-addr                                                                                         addr to advertise for Swarm (default: detect and use the machine IP)   --swarm-discovery                                                                                    Discovery service to use with Swarm   --swarm-experimental                                                                                 Enable Swarm experimental features   --swarm-host "tcp://0.0.0.0:3376"                                                                    ip/socket to listen on for Swarm master   --swarm-image "swarm:latest"                                                                         Specify Docker image to use for Swarm [$MACHINE_SWARM_IMAGE]   --swarm-master                                                                                       Configure Machine to be a Swarm master   --swarm-opt [--swarm-opt option --swarm-opt option]                                                  Define arbitrary flags for swarm   --swarm-strategy "spread"                                                                            Define a default scheduling strategy for Swarm   --virtualbox-boot2docker-url                                                                         The URL of the boot2docker image. Defaults to the latest available version [$VIRTUALBOX_BOOT2DOCKER_URL]   --virtualbox-cpu-count "1"                                                                           number of CPUs for the machine (-1 to use the number of CPUs available) [$VIRTUALBOX_CPU_COUNT]   --virtualbox-disk-size "20000"                                                                       Size of disk for host in MB [$VIRTUALBOX_DISK_SIZE]   --virtualbox-host-dns-resolver                                                                       Use the host DNS resolver [$VIRTUALBOX_HOST_DNS_RESOLVER]   --virtualbox-dns-proxy                                                                               Proxy all DNS requests to the host [$VIRTUALBOX_DNS_PROXY]   --virtualbox-hostonly-cidr "192.168.99.1/24"                                                         Specify the Host Only CIDR [$VIRTUALBOX_HOSTONLY_CIDR]   --virtualbox-hostonly-nicpromisc "deny"                                                              Specify the Host Only Network Adapter Promiscuous Mode [$VIRTUALBOX_HOSTONLY_NIC_PROMISC]   --virtualbox-hostonly-nictype "82540EM"                                                              Specify the Host Only Network Adapter Type [$VIRTUALBOX_HOSTONLY_NIC_TYPE]   --virtualbox-import-boot2docker-vm                                                                   The name of a Boot2Docker VM to import   --virtualbox-memory "1024"                                                                           Size of memory for host in MB [$VIRTUALBOX_MEMORY_SIZE]   --virtualbox-no-share                                                                                Disable the mount of your home directory

您可能會(huì)注意到一些標(biāo)志也指定了它們與之關(guān)聯(lián)的環(huán)境變量(位于該行的最左側(cè))。如果這些環(huán)境變量在docker-machine create被調(diào)用時(shí)被設(shè)置,Docker Machine將使用它們作為標(biāo)志的默認(rèn)值。

為創(chuàng)建的Docker引擎指定配置選項(xiàng)

作為創(chuàng)建過(guò)程的一部分,DockerMachine安裝Docker并使用一些合理的默認(rèn)設(shè)置對(duì)其進(jìn)行配置。例如,它允許通過(guò)tcp與基于tls的加密進(jìn)行連接,并且默認(rèn)為存儲(chǔ)驅(qū)動(dòng)程序如果有的話。

在幾種情況下,用戶可能想要為創(chuàng)建的Docker引擎(也稱為Docker 守護(hù)進(jìn)程)自己設(shè)置選項(xiàng)。例如,他們可能希望允許使用守護(hù)進(jìn)程的標(biāo)志連接到他們正在運(yùn)行的注冊(cè)表--insecure-registry。Docker Machine支持通過(guò)create開頭的命令標(biāo)志為創(chuàng)建的引擎配置這些選項(xiàng)--engine

請(qǐng)注意,DockerMachine只是在守護(hù)進(jìn)程上設(shè)置配置的參數(shù),而不為您設(shè)置任何“依賴項(xiàng)”。例如,如果您指定創(chuàng)建的守護(hù)進(jìn)程應(yīng)該使用btrfs作為一個(gè)存儲(chǔ)驅(qū)動(dòng)程序,您仍然必須確保安裝了適當(dāng)?shù)囊蕾図?xiàng),已經(jīng)創(chuàng)建了BTRFS文件系統(tǒng),等等。

下面是一個(gè)示例用法:

$ docker-machine create -d virtualbox \    
--engine-label foo=bar \    
--engine-label spam=eggs \    
--engine-storage-driver overlay \    
--engine-insecure-registry registry.myco.com \
    foobarmachine

這將在VirtualBox中創(chuàng)建一個(gè)在本地運(yùn)行的虛擬機(jī),該虛擬機(jī)使用overlay存儲(chǔ)后端,具有鍵值對(duì)。foo=barspam=eggs作為引擎上的標(biāo)簽,并允許從不安全的注冊(cè)表推舉/拉動(dòng)位于registry.myco.com.您可以通過(guò)檢查docker info*

$ eval $(docker-machine env foobarmachine)$ docker info
Containers: 0Images: 0Storage Driver: overlay...Name: foobarmachine...Labels:
 foo=bar
 spam=eggs
 provider=virtualbox

所支持的標(biāo)志如下:

  • --engine-insecure-registry*具體說(shuō)明不安全注冊(cè)若要允許使用創(chuàng)建的引擎,請(qǐng)執(zhí)行以下操作

  • --engine-registry-mirror*具體說(shuō)明注冊(cè)表鏡像使用

  • --engine-label*具體說(shuō)明標(biāo)簽對(duì)于創(chuàng)建的引擎

  • --engine-storage-driver*具體說(shuō)明存儲(chǔ)驅(qū)動(dòng)程序與發(fā)動(dòng)機(jī)一起使用

如果引擎支持多次指定標(biāo)志(例如with --label),那么Docker Machine也是如此。

--engine-opt,可用于使用語(yǔ)法指定任意守護(hù)進(jìn)程選項(xiàng)。--engine-opt flagname=value.例如,若要指定守護(hù)進(jìn)程應(yīng)使用8.8.8.8作為所有容器的dns服務(wù)器,并始終使用syslog日志驅(qū)動(dòng)器您可以運(yùn)行以下CREATE命令:

$ docker-machine create -d virtualbox \    
--engine-opt dns=8.8.8.8 \    
--engine-opt log-driver=syslog \
    gdns

另外,Docker Machine支持一個(gè)標(biāo)志,--engine-env,它可以使用語(yǔ)法指定要在引擎內(nèi)設(shè)置的任意環(huán)境變量。--engine-env name=value例如,若要指定引擎應(yīng)使用example.com作為代理服務(wù)器,可以運(yùn)行以下CREATE命令:

$ docker-machine create -d virtualbox \    
--engine-env HTTP_PROXY=http://example.com:8080 \    
--engine-env HTTPS_PROXY=https://example.com:8080 \   
--engine-env NO_PROXY=example2.com \
    proxbox

為所創(chuàng)建的計(jì)算機(jī)指定Docker群集選項(xiàng)

除了能夠配置上面列出的Docker引擎選項(xiàng)之外,您還可以使用Machine指定應(yīng)該如何配置所創(chuàng)建的Swarm主機(jī)。有一個(gè)--swarm-strategy標(biāo)志,您可以使用它來(lái)指定Docker Swarm應(yīng)該使用的調(diào)度策略(機(jī)器默認(rèn)為spread策略)。還有一個(gè)通用--swarm-opt選項(xiàng),它與上述--engine-opt選項(xiàng)類似,只是它指定了用于swarm manage命令(用于引導(dǎo)主節(jié)點(diǎn))而不是基本命令的選項(xiàng)。您可以使用它來(lái)配置強(qiáng)大的用戶可能感興趣的功能,例如配置心跳間隔或Swarm過(guò)度提交資源的意愿。還有一個(gè)--swarm-experimental標(biāo)志,允許你訪問(wèn)Docker Swarm中的實(shí)驗(yàn)性功能。

如果您不確定如何配置這些選項(xiàng),最好不要指定配置。DockerMachine會(huì)為您選擇合理的默認(rèn)設(shè)置,您不必?fù)?dān)心。

示例創(chuàng)建:

$ docker-machine create -d virtualbox \    
--swarm \    
--swarm-master \    
--swarm-discovery token://<token> \    
--swarm-strategy binpack \   
--swarm-opt heartbeat=5s \
    upbeat

這將將群集調(diào)度策略設(shè)置為“binpack”%28pack,在每個(gè)主機(jī)中盡可能嚴(yán)格地將其分配到容器中,而不是將它們分散到%29,“心跳”間隔為5秒。

預(yù)創(chuàng)建檢查

由于許多驅(qū)動(dòng)程序需要一定的條件才能成功執(zhí)行創(chuàng)建(例如,應(yīng)安裝VirtualBox或提供的API憑據(jù)應(yīng)該有效),Docker Machine會(huì)指定一個(gè)“預(yù)創(chuàng)建檢查”在司機(jī)一級(jí)。

如果此預(yù)創(chuàng)建檢查成功,Docker Machine將按正常方式繼續(xù)創(chuàng)建.。如果預(yù)創(chuàng)建檢查失敗,DockerMachine進(jìn)程將退出狀態(tài)代碼3,以指示非零退出的源是預(yù)創(chuàng)建檢查失敗。

Previous article: Next article: