docker + weave + QAServer

build.sh

# /bin/sh
docker build -t springcloud .

docker-compose.yml

version: "3"

services:
  nameServer:
    image: ccr.ccs.tencentyun.com/demons/qaserver:v2
    deploy:
      replicas: 1
      # 控制重启条件，解决应用启动时间过长导致的容器被杀死
      restart_policy:
        condition: on-failure
        delay: 5s
        max_attempts: 3
        window: 20m
    working_dir: /home/QAServer/nameServer
    entrypoint:
      - /bin/bash
      - -c
      - "git pull && mvn spring-boot:run"
    ports:
      - 1111:1111
    networks:
      weave:
        aliases:
          - nameServer
    # healthcheck:
    #   test: ["CMD-SHELL", "curl --fail http://localhost:1111/info"]
    #   interval: 2s
    #   timeout: 2s
    #   retries: 3

  apiGateway:
    image: ccr.ccs.tencentyun.com/demons/qaserver:v2
    deploy:
      replicas: 1
      restart_policy:
        condition: on-failure
        delay: 5s
        max_attempts: 3
        window: 20m
    working_dir: /home/QAServer/apiGateway
    entrypoint:
      - /bin/bash
      - -c
      - "git pull && mvn spring-boot:run"
    ports:
      - 8443:8443
    networks:
      weave:
        aliases:
          - apiGateway
    # healthcheck:
    #   test: ["CMD-SHELL", "curl --fail -k https://localhost:8443/info"]
    #   interval: 10m
    #   timeout: 2s
    #   retries: 3

  visualizer:
    deploy:
      replicas: 1
    image: dockersamples/visualizer:stable
    ports:
      - "8080:8080"
    volumes:
      - "/var/run/docker.sock:/var/run/docker.sock"
    deploy:
      placement:
        constraints: [node.role == manager]
    networks:
      - weave

  recommend:
    image: ccr.ccs.tencentyun.com/demons/qaserver:v2
    deploy:
      replicas: 1
      restart_policy:
        condition: on-failure
        delay: 5s
        max_attempts: 3
        window: 20m
    working_dir: /home/QAServer/recommend
    entrypoint:
      - /bin/bash
      - -c
      - "git pull && mvn spring-boot:run"
    networks:
      weave:
        aliases:
          - recommend
    # healthcheck:
    #   test: ["CMD-SHELL", "curl --fail http://localhost:2345/info"]
    #   interval: 10m
    #   timeout: 5s
    #   retries: 3

  qa:
    image: ccr.ccs.tencentyun.com/demons/qaserver:v2
    deploy:
      replicas: 1
      restart_policy:
        condition: on-failure
        delay: 5s
        max_attempts: 3
        window: 20m
    working_dir: /home/QAServer/qa
    entrypoint:
      - /bin/bash
      - -c
      - "git pull && mvn spring-boot:run"
    networks:
      weave:
        aliases:
          - qa
    # healthcheck:
    #   test: ["CMD-SHELL", "curl --fail http://localhost:2346/info"]
    #   interval: 10m
    #   timeout: 2s
    #   retries: 3

  topic:
    deploy:
      replicas: 1
    image: ccr.ccs.tencentyun.com/demons/qaserver:v2
    deploy:
      replicas: 1
      restart_policy:
        condition: on-failure
        delay: 5s
        max_attempts: 3
        window: 20m
    working_dir: /home/QAServer/topic
    entrypoint:
      - /bin/bash
      - -c
      - "git pull && mvn spring-boot:run"
    networks:
      weave:
        aliases:
          - topic
    # healthcheck:
    #   test: ["CMD-SHELL", "curl --fail http://localhost:2349/info"]
    #   interval: 3m
    #   timeout: 5s
    #   retries: 3

  studio:
    image: ccr.ccs.tencentyun.com/demons/qaserver:v2
    deploy:
      replicas: 1
      restart_policy:
        condition: on-failure
        delay: 5s
        max_attempts: 3
        window: 20m
    working_dir: /home/QAServer/studio
    entrypoint:
      - /bin/bash
      - -c
      - "git pull && mvn spring-boot:run"
    networks:
      weave:
        aliases:
          - studio
    # healthcheck:
    #   test: ["CMD-SHELL", "curl --fail http://localhost:2347/info"]
    #   interval: 3m
    #   timeout: 5s
    #   retries: 3

  owner:
    image: ccr.ccs.tencentyun.com/demons/qaserver:v2
    deploy:
      replicas: 1
      restart_policy:
        condition: on-failure
        delay: 5s
        max_attempts: 3
        window: 20m
    working_dir: /home/QAServer/owner
    entrypoint:
      - /bin/bash
      - -c
      - "git pull && mvn spring-boot:run"
    networks:
      weave:
        aliases:
          - owner
    # healthcheck:
    #   test: ["CMD-SHELL", "curl --fail http://localhost:2355/info"]
    #   interval: 3m
    #   timeout: 5s
    #   retries: 3

networks:
  weave:
    driver: overlay

Dockerfile

FROM maven:latest
MAINTAINER demons 837940593@qq.com

ADD settings.xml /usr/share/maven/conf/settings.xml

ADD sources.list /etc/apt/sources.list
RUN apt-get update
RUN apt-get install -y vim
RUN apt-get install -y git

RUN cd /home && git clone https://github.com/Clcanny/QAServer.git

# WORKDIR /home/QAServer
# RUN cd nameServer && mvn package -Dmaven.test.skip=true
# RUN cd apiGateway && mvn package -Dmaven.test.skip=true
# RUN cd recommend && mvn package -Dmaven.test.skip=true
# RUN cd qa && mvn package -Dmaven.test.skip=true
# RUN cd topic && mvn package -Dmaven.test.skip=true
# RUN cd studio && mvn package -Dmaven.test.skip=true
# RUN cd owner && mvn package -Dmaven.test.skip=true

dockerRegistry

# 只能本地使用，存在很大局限性
# Start your registry
docker run -d -p 5000:5000 --name registry registry:2

# Tag the image so that it points to your registry
docker tag springcloud localhost:5000/qaserver:v2

# Push it to local registry/repo
docker push localhost:5000/qaserver:v2

# For verification you can use this command:
curl -X GET http://localhost:5000/v2/_catalog
# It will print out all images on repo.

# On private registry machine add additional parameters to enable insecure repo:
ExecStart=/usr/bin/dockerd --insecure-registry IP_OF_CURRENT_MACHINE:5000

# In docker-compose.yml, localhost:5000/qaserver:v2

installDockerOnDebian8.sh

# /bin/sh
sudo apt-get install --assume-yes \
    apt-transport-https \
    ca-certificates \
    curl \
    python-software-properties \
    software-properties-common
curl -fsSL https://download.docker.com/linux/debian/gpg | sudo apt-key add -
sudo apt-key fingerprint 0EBFCD88
sudo add-apt-repository \
    "deb [arch=amd64] https://download.docker.com/linux/debian \
    $(lsb_release -cs) \
    stable"
deb-src [arch=amd64] https://download.docker.com/linux/debian wheezy stable
sudo apt-get update
sudo apt-get install -y docker-ce
curl -sSL https://get.daocloud.io/daotools/set_mirror.sh | sh -s http://ba894f51.m.daocloud.io
sudo service docker restart
sudo usermod -aG docker $USER

installWeave.sh

# /bin/bash
sudo curl -L git.io/weave -o /usr/local/bin/weave
sudo chmod a+x /usr/local/bin/weave

# 选定某个主机作为master节点，最好该主机也是nameServer运行的主机，比如说是119.28.137.112
weave launch
# 对于其它主机
weave launch 119.28.137.112
# 对于所有的主机，执行以测试状态
weave status connections

runDocker

# 使用weave不需要prefer-ip-address配置

# 对外开放端口
docker run --net=weave -h nameServer.weave.local $(weave dns-args) --name nameServer -d -p 1111:1111 springcloud /bin/bash -c "cd /home/QAServer/nameServer; git pull; mvn spring-boot:run"
docker run --net=weave -h apiGateway.weave.local $(weave dns-args) --name apiGateway -d -p 8443:8443 springcloud /bin/bash -c "cd /home/QAServer/apiGateway; git pull; mvn spring-boot:run"

# 对外不开放端口
docker run --net=weave -h recommend.weave.local $(weave dns-args) --name recommend --health-cmd "curl --fail http://localhost:2345/info || exit 1" --health-interval=20s --health-timeout=5s -d springcloud /bin/bash -c "cd /home/QAServer/recommend; git pull; mvn spring-boot:run"
docker run --net=weave -h qa.weave.local $(weave dns-args) --name qa --health-cmd "curl --fail http://localhost:2346/info || exit 1" --health-interval=20s --health-timeout=5s -d springcloud /bin/bash -c "cd /home/QAServer/qa; git pull; mvn spring-boot:run"
docker run --net=weave -h topic.weave.local $(weave dns-args) --name topic --health-cmd "curl --fail http://localhost:2349/info || exit 1" --health-interval=20s --health-timeout=5s -d springcloud /bin/bash -c "cd /home/QAServer/topic; git pull; mvn spring-boot:run"
docker run --net=weave -h studio.weave.local $(weave dns-args) --name studio --health-cmd "curl --fail http://localhost:2347/info || exit 1" --health-interval=20s --health-timeout=5s -d springcloud /bin/bash -c "cd /home/QAServer/studio; git pull; mvn spring-boot:run"
docker run --net=weave -h owner.weave.local $(weave dns-args) --name owner --health-cmd "curl --fail http://localhost:2355/info || exit 1" --health-interval=10s --health-timeout=5s -d springcloud /bin/bash -c "cd /home/QAServer/owner; git pull; mvn spring-boot:run"
docker run --net=weave -h storage.weave.local $(weave dns-args) --name storage -d -p 6666:6666 springcloud /bin/bash -c "cd /home/QAServer/storage; git pull; mvn spring-boot:run"

settings.xml

<?xml version="1.0" encoding="UTF-8"?>

<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
-->

<!--
 | This is the configuration file for Maven. It can be specified at two levels:
 |
 |  1. User Level. This settings.xml file provides configuration for a single user,
 |                 and is normally provided in ${user.home}/.m2/settings.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -s /path/to/user/settings.xml
 |
 |  2. Global Level. This settings.xml file provides configuration for all Maven
 |                 users on a machine (assuming they're all using the same Maven
 |                 installation). It's normally provided in
 |                 ${maven.conf}/settings.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -gs /path/to/global/settings.xml
 |
 | The sections in this sample file are intended to give you a running start at
 | getting the most out of your Maven installation. Where appropriate, the default
 | values (values used when the setting is not specified) are provided.
 |
 |-->
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
  <!-- localRepository
   | The path to the local repository maven will use to store artifacts.
   |
   | Default: ${user.home}/.m2/repository
  <localRepository>/path/to/local/repo</localRepository>
  -->

  <!-- interactiveMode
   | This will determine whether maven prompts you when it needs input. If set to false,
   | maven will use a sensible default value, perhaps based on some other setting, for
   | the parameter in question.
   |
   | Default: true
  <interactiveMode>true</interactiveMode>
  -->

  <!-- offline
   | Determines whether maven should attempt to connect to the network when executing a build.
   | This will have an effect on artifact downloads, artifact deployment, and others.
   |
   | Default: false
  <offline>false</offline>
  -->

  <!-- pluginGroups
   | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
   | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
   | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
   |-->
  <pluginGroups>
    <!-- pluginGroup
     | Specifies a further group identifier to use for plugin lookup.
    <pluginGroup>com.your.plugins</pluginGroup>
    -->
  </pluginGroups>

  <!-- proxies
   | This is a list of proxies which can be used on this machine to connect to the network.
   | Unless otherwise specified (by system property or command-line switch), the first proxy
   | specification in this list marked as active will be used.
   |-->
  <proxies>
    <!-- proxy
     | Specification for one proxy, to be used in connecting to the network.
     |
    <proxy>
      <id>optional</id>
      <active>true</active>
      <protocol>http</protocol>
      <username>proxyuser</username>
      <password>proxypass</password>
      <host>proxy.host.net</host>
      <port>80</port>
      <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
    </proxy>
    -->
  </proxies>

  <!-- servers
   | This is a list of authentication profiles, keyed by the server-id used within the system.
   | Authentication profiles can be used whenever maven must make a connection to a remote server.
   |-->
  <servers>
    <!-- server
     | Specifies the authentication information to use when connecting to a particular server, identified by
     | a unique name within the system (referred to by the 'id' attribute below).
     |
     | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
     |       used together.
     |
    <server>
      <id>deploymentRepo</id>
      <username>repouser</username>
      <password>repopwd</password>
    </server>
    -->

    <!-- Another sample, using keys to authenticate.
    <server>
      <id>siteServer</id>
      <privateKey>/path/to/private/key</privateKey>
      <passphrase>optional; leave empty if not used.</passphrase>
    </server>
    -->
  </servers>

  <!-- mirrors
   | This is a list of mirrors to be used in downloading artifacts from remote repositories.
   |
   | It works like this: a POM may declare a repository to use in resolving certain artifacts.
   | However, this repository may have problems with heavy traffic at times, so people have mirrored
   | it to several places.
   |
   | That repository definition will have a unique id, so we can create a mirror reference for that
   | repository, to be used as an alternate download site. The mirror site will be the preferred
   | server for that repository.
   |-->
  <mirrors>
    <!-- mirror
     | Specifies a repository mirror site to use instead of a given repository. The repository that
     | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
     | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
     |
    <mirror>
      <id>mirrorId</id>
      <mirrorOf>repositoryId</mirrorOf>
      <name>Human Readable Name for this Mirror.</name>
      <url>http://my.repository.com/repo/path</url>
    </mirror>
     -->
    <mirror>
        <id>nexus-aliyun</id>
        <mirrorOf>*</mirrorOf>
        <name>Nexus aliyun</name>
        <url>http://maven.aliyun.com/nexus/content/groups/public</url>
    </mirror>
  </mirrors>

  <!-- profiles
   | This is a list of profiles which can be activated in a variety of ways, and which can modify
   | the build process. Profiles provided in the settings.xml are intended to provide local machine-
   | specific paths and repository locations which allow the build to work in the local environment.
   |
   | For example, if you have an integration testing plugin - like cactus - that needs to know where
   | your Tomcat instance is installed, you can provide a variable here such that the variable is
   | dereferenced during the build process to configure the cactus plugin.
   |
   | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
   | section of this document (settings.xml) - will be discussed later. Another way essentially
   | relies on the detection of a system property, either matching a particular value for the property,
   | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
   | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
   | Finally, the list of active profiles can be specified directly from the command line.
   |
   | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
   |       repositories, plugin repositories, and free-form properties to be used as configuration
   |       variables for plugins in the POM.
   |
   |-->
  <profiles>
    <!-- profile
     | Specifies a set of introductions to the build process, to be activated using one or more of the
     | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
     | or the command line, profiles have to have an ID that is unique.
     |
     | An encouraged best practice for profile identification is to use a consistent naming convention
     | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
     | This will make it more intuitive to understand what the set of introduced profiles is attempting
     | to accomplish, particularly when you only have a list of profile id's for debug.
     |
     | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
    <profile>
      <id>jdk-1.4</id>

      <activation>
        <jdk>1.4</jdk>
      </activation>

      <repositories>
        <repository>
          <id>jdk14</id>
          <name>Repository for JDK 1.4 builds</name>
          <url>http://www.myhost.com/maven/jdk14</url>
          <layout>default</layout>
          <snapshotPolicy>always</snapshotPolicy>
        </repository>
      </repositories>
    </profile>
    -->

    <!--
     | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
     | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
     | might hypothetically look like:
     |
     | ...
     | <plugin>
     |   <groupId>org.myco.myplugins</groupId>
     |   <artifactId>myplugin</artifactId>
     |
     |   <configuration>
     |     <tomcatLocation>${tomcatPath}</tomcatLocation>
     |   </configuration>
     | </plugin>
     | ...
     |
     | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
     |       anything, you could just leave off the <value/> inside the activation-property.
     |
    <profile>
      <id>env-dev</id>

      <activation>
        <property>
          <name>target-env</name>
          <value>dev</value>
        </property>
      </activation>

      <properties>
        <tomcatPath>/path/to/tomcat/instance</tomcatPath>
      </properties>
    </profile>
    -->
  </profiles>

  <!-- activeProfiles
   | List of profiles that are active for all builds.
   |
  <activeProfiles>
    <activeProfile>alwaysActiveProfile</activeProfile>
    <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  </activeProfiles>
  -->
</settings>

sources.list

deb http://mirrors.163.com/debian/ jessie main non-free contrib
deb http://mirrors.163.com/debian/ jessie-updates main non-free contrib
deb http://mirrors.163.com/debian/ jessie-backports main non-free contrib
deb-src http://mirrors.163.com/debian/ jessie main non-free contrib
deb-src http://mirrors.163.com/debian/ jessie-updates main non-free contrib
deb-src http://mirrors.163.com/debian/ jessie-backports main non-free contrib
deb http://mirrors.163.com/debian-security/ jessie/updates main non-free contrib
deb-src http://mirrors.163.com/debian-security/ jessie/updates main non-free contrib

docker ps -a | awk '{ print $1,$2 }' | grep localhost:5000/qaserver:v2 | awk '{print $1 }' | xargs -I {} sudo docker rm {}

docker stack deploy -c docker-compose.yml qaserver
docker service ls