1.Deployment
Portainer is built to run on Docker and is really simple to deploy.
Portainer deployment scenarios can be executed on any platform unless specified.
Quick start
Deploying Portainer is as simple as:
$ docker run -d -p 9000:9000 portainer/portainer
Voilà, you can now access Portainer by pointing your web browser at http://DOCKER_HOST:9000
Ensure you replace DOCKER_HOST with address of your Docker host where Portainer is running.
You‘ll then be prompted to specify a new password for the admin account. After specifying your password, you‘ll then be able to connect to the Portainer UI.
Manage a new endpoint
After your first authentication, Portainer will ask you information about the Docker endpoint you want to manage.
You‘ll have the following choices:
Not available for Windows Containers (Windows Server 2016) - Manage the local engine where Portainer is running (you‘ll need to bind mount the Docker socket via -v /var/run/docker.sock:/var/run/docker.sock on the Docker CLI when running Portainer)
Manage a remote Docker engine, you‘ll just have to specify the url to your Docker endpoint, give it a name and TLS info if needed
Declare initial endpoint via CLI
You can specify the initial endpoint you want Portainer to manage via the CLI, use the -H flag and the tcp:// protocol to connect to a remote Docker endpoint:
$ docker run -d -p 9000:9000 portainer/portainer -H tcp://<REMOTE_HOST>:<REMOTE_PORT>
Ensure you replace REMOTE_HOST and REMOTE_PORT with the address/port of the Docker engine you want to manage.
You can also bind mount the Docker socket to manage a local Docker engine (not available for Windows Containers (Windows Server 2016)):
$ docker run -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer
Note: If your host is using SELinux, you‘ll need to pass the --privileged flag to the Docker run command:
$ docker run -d -p 9000:9000 --privileged -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer
Connect to a Swarm cluster
Portainer will automatically detect if your endpoint is part of a Swarm cluster (either Docker Swarm or Swarm mode).
Note: Ensure you connect to either a primary node when connecting to a Docker Swarm cluster or a manager node when connecting to a cluster created with Docker swarm mode.
As simple as:
$ docker run -d -p 9000:9000 portainer/portainer -H tcp://<SWARM_MANAGER_IP>:2375
Alternatively, if you‘re using swarm mode, you can also deploy it as a service in your cluster:
$ docker service create \
--name portainer \
--publish 9000:9000 \
--constraint ‘node.role == manager‘ \
--mount type=bind,src=//var/run/docker.sock,dst=/var/run/docker.sock \
portainer/portainer \
-H unix:///var/run/docker.sock
Connect to a Docker engine with TLS enabled
If your Docker engine is protected using TLS, you‘ll need to ensure that you have access to CA, the certificate and the public key used to access your Docker engine.
You can upload the required files via the Portainer UI or use the --tlsverify flag on the CLI.
Portainer will try to use the following paths to the files specified previously (on Linux, see the configuration section for details about Windows):
CA: /certs/ca.pem
certificate: /certs/cert.pem
public key: /certs/key.pem
You must ensure these files are present in the container using a bind mount:
$ docker run -d -p 9000:9000 -v /path/to/certs:/certs portainer/portainer -H tcp://<DOCKER_HOST>:<DOCKER_PORT> --tlsverify
You can also use the --tlscacert, --tlscert and --tlskey flags if you want to change the default path to the CA, certificate and key file respectively:
$ docker run -d -p 9000:9000 -v /path/to/certs:/certs portainer/portainer -H tcp://<DOCKER_HOST>:<DOCKER_PORT> --tlsverify --tlscacert /certs/myCa.pem --tlscert /certs/myCert.pem --tlskey /certs/myKey.pem
Persist Portainer data
By default, Portainer will store its data inside the container in the /data folder on Linux (C:\data on Windows, this can be changed via CLI, see configuration).
You‘ll need to persist Portainer data to keep your changes after restart/upgrade of the Portainer container. You can use a bind mount to persist the data on the Docker host folder:
$ docker run -d -p 9000:9000 -v /path/on/host/data:/data portainer/portainer
On Windows:
$ docker run -d -p 9000:9000 -v C:\ProgramData\Portainer:C:\data portainer/portainer:windows
If you deployed Portainer as a Docker Swarm service:
$ docker service create \
--name portainer \
--publish 9000:9000 \
--constraint ‘node.role == manager‘ \
--mount type=bind,src=/var/run/docker.sock,dst=/var/run/docker.sock \
--mount type=bind,src=/path/on/host/data,dst=/data \
portainer/portainer \
-H unix:///var/run/docker.sock
Secure Portainer using SSL
By default, Portainer‘s web interface and API is exposed over HTTP. This is not secured, it‘s recommended to enable SSL in a production environment.
To do so, you can use the following flags --ssl, --sslcert and --sslkey:
$ docker run -p 443:9000 -v ~/local-certs:/certs portainer --ssl --sslcert /certs/portainer.crt --sslkey /certs/portainer.key
You can use the following commands to generate the required files:
$ openssl genrsa -out portainer.key 2048
$ openssl ecparam -genkey -name secp384r1 -out portainer.key
$ openssl req -new -x509 -sha256 -key portainer.key -out portainer.crt -days 3650
Note that Certbot could be used as well to generate a certificate and a key.
Without Docker
Portainer binaries are available on each release page: Portainer releases
Download and extract the binary to a location on disk:
$ cd /opt
$ wget https://github.com/portainer/portainer/releases/download/1.13.1/portainer-1.13.1-linux-amd64.tar.gz
$ tar xvpfz portainer-1.13.1-linux-amd64.tar.gz
Then just use the portainer binary as you would use CLI flags with Docker.
Note: Portainer will try to write its data into the /data folder by default. You must ensure this folder exists first.
$ mkdir /data
$ cd /opt
$ ./portainer/portainer
You can use the -p flag to serve Portainer on another port:
$ ./portainer/portainer -p :8080
You can change the folder used by Portainer to store its data with the -d flag:
$ ./portainer/portainer -d /opt/portainer-data
2.docker comand
docker rm $(docker ps -a -q)
curl -sSL https://shipyard-project.com/deploy | bash -s
3.docker Swarm
Docker - 配置国内加速器加速镜像下载。
引言
由于网络原因，我们在pull Image 的时候，从Docker Hub上下载会很慢。。。所以，国内的Docker爱好者们就添加了一一些国内的镜像（mirror）,方便大家使用。
配置阿里云加速器
1. 登录阿里开发者平台：https://dev.aliyun.com/search.html
2. 点击“创建我的容器镜像”
3. 注册/登录后，进入Docker 镜像仓库 (https://cr.console.aliyun.com/#/imageList)，选中加速器 Tab
这里可以看到，系统已经为我们生成了一个专属加速器地址：https://xxxxx.mirror.aliyuncs.com
4. 根据个人需要, 选择运行Docker 的OS，按照要求修改Docker配置文件
我这里的OS是CentOS, docker版本是1.12， 所以步骤如下：
修改配制文件 : vim usr/lib/systemd/system/docker.service
添加红色部分到 "ExecStart" ExecStart=/usr/bin/dockerd --registry-mirror=<your accelerate address>
保存文件
重新加载配制：$ systemctl daemon-reload
重新启动服务：$ service docker restart
验证
在Docker client 上面Pull 一个 MySQL， 看看速度如何