Docker Compose (Docker Stack)

image: Specify the image to start the container from. Can either be a repository/tag or a partial image ID.
If the image does not exist, Compose attempts to pull it, unless you have also specified build, in which case it builds it using the specified options and tags it with the specified tag.

deploy: (resource limits) This only takes effect when deploying to a swarm with docker stack deploy, and is ignored by docker-compose up and docker-compose run.

depends_on: Express dependency between services. Service dependencies cause the following behaviors:

networks: Networks to join, referencing entries under the top-level networks key.

ports: (Port mapping) Either specify both ports (HOST:CONTAINER), or just the container port (an ephemeral host port is chosen).

environment: Environment variables with only a key are resolved to their values on the machine Compose is running on, which can be helpful for secret or host-specific values.
environment:
- SHOW=true
- SESSION_SECRET

volumes: bind mount, named volume
When you use a bind mount, a file or directory on the host machine is mounted into a container. The file or directory is referenced by its absolute path on the host machine. By contrast, when you use a volume, a new directory is created within Docker's storage directory on the host machine, and Docker manages that directory's contents. Volumes have several advantages over bind mounts.
The source of the mount. For bind mounts, this is the path to the file or directory on the Docker daemon host. May be specified as source or src.
The destination takes as its value the path where the file or directory is mounted in the container. May be specified as destination, dst, or target.

logging: The default driver json-file, has options to limit the amount of logs stored. To do this, use a key-value pair for maximum storage size and maximum number of files:
options:
max-size: "200k"
max-file: "10"
The example shown above would store log files until they reach a max-size of 200kB, and then rotate them. As logs grow beyond the max limits, older log files are removed to allow storage of new logs.

docker-stack.yml

# docker stack deploy -c docker-stack.yml

version: "3.5"
x-logging:
&graylog-logging
driver: gelf
options:
gelf-address: "udp://graylog-svc:12201" x-default-logging:
&default-logging
driver: json-file x-deploy:
&default-limits
resources:
limits:
memory: 256M x-environment:
&rcs-config-server-url
RCS_CONFIG_SERVER_URL=http://config-server:19050/config services:
redis:
image: "redis:latest"
# logging: *graylog-logging
deploy: *default-limits
networks:
- outside
ports:
- "6379:6379"
volumes:
- /u/docker/redis/config:/usr/local/etc/redis # service name: prime_config-server
config-server:
image: "dck0.prime/prime-rcs-config-server:${RCS_CONFIG_VERSION:-0.0.1-SNAPSHOT}"
# logging: *graylog-logging
deploy: *default-limits
networks:
- outside
ports:
- "19050:19050"
environment:
- RCS_CONFIG_SERVER_LOCATION=file:/assert/config
- RCS_KEYSTORE_LOCATION=file:/assert/server.jks
- RCS_KEYSTORE_ALIAS=sz-qa-env
env_file: "$HOME/.ssh/rcs_keystore.env"
volumes:
- ./server.jks:/assert/server.jks:/ro
- ~/workspace/devops/prime-config/qa/qa:/assert/config/:/ro pmc-backend:
image: "dck0.prime/prime-management-console:${PMC_BACKEND_VERSION:-0.0.1-SNAPSHOT}"
# logging: *graylog-logging
deploy: *default-limits
depends_on:
- config-server
- redis
networks:
- outside
ports:
- "8283:8283"
environment:
- PMC_CONFIG_CLIENT_URL=http://config-server:19050/config
- PMC_CONFIG_CLIENT_PROFILE=qa
- LOGBACK_LOGSTASH_URL=10.102.129.23:5044
- APM_AGENT_ACTIVE=true
volumes:
- /u/docker/nginx/html/logs/pmc:/prime/logs/pmc
- /u/docker/nginx/html/upload:/opt/pmc/upload mission-mgr:
image: "dck0.prime/prime-rcs-mission:${RCS_MISSION_VERSION:-0.0.1-SNAPSHOT}"
# logging: *graylog-logging
deploy: *default-limits
depends_on:
- config-server
networks:
- outside
ports:
- "19030:19030"
- "16002:16002"
environment:
- *rcs-config-server-url
- RCS_CONFIG_CLIENT_PROFILE=qa
- LOGBACK_LOGSTASH_URL=10.102.129.23:5044
- APM_AGENT_ACTIVE=true
- JPDA_ADDRESS=16002
- JPDA_TRANSPORT=dt_socket
volumes:
- /u/docker/nginx/html/logs/rcs:/rcs/logs
- /u/docker/rcs/mission/script:/rcs/uploads/mission-script traffic-mgr:
image: "dck0.prime/prime-rcs-traffic-manager:${RCS_TRAFFIC_VERSION:-0.0.1-SNAPSHOT}"
# logging: *graylog-logging
deploy: *default-limits
depends_on:
- config-server
networks:
- outside
ports:
- "19090:19090"
- "16001:16001"
environment:
- *rcs-config-server-url
- RCS_CONFIG_CLIENT_PROFILE=qa
- LOGBACK_LOGSTASH_URL=10.102.129.23:5044
- APM_AGENT_ACTIVE=true
- JPDA_ADDRESS=16001
- JPDA_TRANSPORT=dt_socket
volumes:
- /u/docker/nginx/html/logs/rcs:/rcs/logs battery-mgr:
image: "dck0.prime/prime-rcs-battery-manager:${RCS_BATTERY_VERSION:-0.0.1-SNAPSHOT}"
# logging: *graylog-logging
deploy: *default-limits
depends_on:
- config-server
networks:
- outside
ports:
- "19040:19040"
environment:
- *rcs-config-server-url
- RCS_CONFIG_CLIENT_PROFILE=qa
- LOGBACK_LOGSTASH_URL=10.102.129.23:5044
- APM_AGENT_ACTIVE=true
volumes:
- /u/docker/nginx/html/logs/rcs:/rcs/logs simulator-mgr:
image: "dck0.prime/prime-rcs-simulator:${RCS_SIMULATOR_VERSION:-0.0.1-SNAPSHOT}"
# logging: *graylog-logging
deploy: *default-limits
depends_on:
- config-server
networks:
- outside
ports:
- "18010:18010"
environment:
- *rcs-config-server-url
- RCS_CONFIG_CLIENT_PROFILE=qa
- LOGBACK_LOGSTASH_URL=10.102.129.23:5044
- APM_AGENT_ACTIVE=true
volumes:
- /u/docker/nginx/html/logs/rcs:/rcs/logs error-mgr:
image: "dck0.prime/prime-rcs-error:${RCS_SIMULATOR_VERSION:-0.0.1-SNAPSHOT}"
# logging: *graylog-logging
deploy: *default-limits
depends_on:
- config-server
networks:
- outside
ports:
- "18040:18040"
environment:
- *rcs-config-server-url
- RCS_CONFIG_CLIENT_PROFILE=qa
- LOGBACK_LOGSTASH_URL=10.102.129.23:5044
- APM_AGENT_ACTIVE=true
volumes:
- /u/docker/nginx/html/logs/rcs:/rcs/logs eshelf-mgr:
image: "dck0.prime/prime-rcs-eshelf:${RCS_ESHELF_VERSION:-0.0.1-SNAPSHOT}"
# logging: *graylog-logging
deploy: *default-limits
depends_on:
- config-server
networks:
- outside
ports:
- "19110:19110"
environment:
- *rcs-config-server-url
- RCS_CONFIG_CLIENT_PROFILE=qa
volumes:
- /u/docker/nginx/html/logs/rcs:/rcs/logs path-plan:
image: "dck0.prime/prime-rcs-path-plan:${RCS_PATH_PLAN_VERSION:-0.0.1-SNAPSHOT}"
# logging: *graylog-logging
deploy: *default-limits
networks:
- outside
ports:
- "18020:80"
environment:
- RCS_MISSION_SERVER=http://mission-mgr:19030
volumes:
- /u/docker/nginx/html/logs/rcs:/RcsPathPlan/logs ticket-mgr:
image: "dck0.prime/prime-web-service:latest"
# logging: *graylog-logging
deploy: *default-limits
networks:
- outside
ports:
- "3000:3000" # prime-rcs-authentication:
# image: "dck0.prime/prime-rcs-authentication:0.0.1-SNAPSHOT"
# # logging: *graylog-logging
# deploy: *default-limits
# networks:
# - outside
# ports:
# - "8090:8090" # prime-rcs-auth2-web:
# image: "dck0.prime/prime-rcs-auth2-web:0.0.1-SNAPSHOT"
# # logging: *graylog-logging
# deploy: *default-limits
# networks:
# - outside
# ports:
# - "8091:8091" asc-bridge:
image: "dck0.prime/prime-asc-bridge:1.0-SNAPSHOT"
# logging: *graylog-logging
deploy: *default-limits
depends_on:
- config-server
networks:
- outside
ports:
- "19080:19080"
volumes:
- /u/docker/nginx/html/logs/rcs:/rcs/logs
environment:
- *rcs-config-server-url
- RCS_CONFIG_CLIENT_PROFILE=qa
- LOGBACK_LOGSTASH_URL=10.102.129.23:5044 networks:
outside:
external: true
name: qa-subnet

Docker Stack 笔记的更多相关文章

  1. Docker Stack 学习笔记

    该文为<深入浅出Docker>的学习笔记,感谢查看,如有错误,欢迎指正 一.简介 Docker Stack 是为了解决大规模场景下的多服务部署和管理,提供了期望状态,滚动升级,简单易用,扩 ...

  2. docker stack 部署 mssql

    =============================================== 2019/12/8_第1次修改                       ccb_warlock == ...

  3. Docker学习笔记 — 配置国内免费registry mirror

    Docker学习笔记 — 配置国内免费registry mirror Docker学习笔记 — 配置国内免费registry mirror

  4. docker学习笔记1 -- 安装和配置

    技术资料 docker中文官网:http://www.docker.org.cn/ 中文入门课程:http://www.docker.org.cn/book/docker.html docker学习笔 ...

  5. Docker学习笔记之一,搭建一个JAVA Tomcat运行环境

    Docker学习笔记之一,搭建一个JAVA Tomcat运行环境 前言 Docker旨在提供一种应用程序的自动化部署解决方案,在 Linux 系统上迅速创建一个容器(轻量级虚拟机)并部署和运行应用程序 ...

  6. docker~学习笔记索引

    回到占占推荐博客索引 使用docker也有段时间了,写了不少文章与总结,下面把它整理个目录出来,方便大家去学习与检索! docker~学习笔记索引 docker~linux下的部署和基本命令(2017 ...

  7. Docker Stack 集群部属服务

    Docker越来越成熟,功能也越来越强大.使用Dokcer Stack做服务集群也是非常的方便,docker 自己就提供了负载功能,感觉很方便,就想给大家分享一下,做一个简单的教程. 环境 我是用了两 ...

  8. Docker学习笔记 - Docker容器内部署redis

    Docker学习笔记(2-4)Docker应用实验-redist server 和client的安装使用 一.获取redis容器(含客户端和服务端) 二.创建服务端容器 1.在终端A中运行redis- ...

  9. docker学习笔记(一)—— ubuntu16.04下安装docker

    docker学习笔记(一)—— ubuntu16.04下安装docker 原创 2018年03月01日 14:53:00 标签: docker / ubuntu 1682 本文开发环境为Ubuntu ...

随机推荐

  1. python模块:excel的读和修改xlrd/xultils

    一.xlrd xlrd只能对excel进行读取,不可编辑修改.该模块属于第三方模块,需要安装模块包并引入.pip install xlrd 常用的方法: import xlrd book = xlrd ...

  2. Java审计之XSS篇

    Java审计之XSS篇 0x00 前言 继续 学习一波Java审计的XSS漏洞的产生过程和代码. 0x01 Java 中XSS漏洞代码分析 xss原理 xss产生过程: 后台未对用户输入进行检查或过滤 ...

  3. 安装模块中出现的问题:不是内部或外部命令、pip 命令不存在、Unknown or unsupported command 'install'

    #cmd下python.pip不是内部或外部命令——表示环境变量没有加# path中新增1.python的安装目录# 2.python下scripts的目录 #提示 pip 命令不存在——表示环境变量 ...

  4. Linux 系统中环境变量/etc/profile、/etc/bashrc、~/.bashrc的区别

      /etc/profile./etc/bashrc.~/.bashrc的区别   1> etc目录下存放系统管理和配置文件 (系统配置) etc/profile:  profile为所有的用户 ...

  5. Mybatis 注解形式

        1.查询 // 查询 @Select("select id, name, type, numbers, cancelled, completed, percentage from c ...

  6. Kubernetes入门(四)——如何在Kubernetes中部署一个可对外服务的Tensorflow机器学习模型

    机器学习模型常用Docker部署,而如何对Docker部署的模型进行管理呢?工业界的解决方案是使用Kubernetes来管理.编排容器.Kubernetes的理论知识不是本文讨论的重点,这里不再赘述, ...

  7. Jmeter引用外部jar包的几种方法

    总结记录下jmeter引用外部jar包的3种方法及其优缺点: 一.测试计划中添加目录或jar包到Classpath 操作:测试计划->添加目录或jar包到Classpath-->浏览导入j ...

  8. 关于KeePass基于csv格式的批量导入与导出

    在KeePass的导出选项中,有一个KeePass CSV(1.x),导出后格式如下: "Account","Login Name","Passwor ...

  9. Oracle学习(十六)Oracle安装

    为了本地创建数据库自己玩耍,还是下个Oracle的客户端吧... 一.下载地址 注意,要用Oracle的帐号进行登录后才能下载 http://download.oracle.com/otn/nt/or ...

  10. PHP绕过disable_function

    PHP绕过disable_function 常规绕过 exec exec执行command命令,但是不会输出全部结果,而是返回结果的最后一行. 想得到全部的结果,可以使用第二个参数,让其输出到一个数组 ...