使用Fig的Docker编排

最新推荐文章于 2024-03-18 09:45:41 发布
最新推荐文章于 2024-03-18 09:45:41 发布
阅读量223 收藏
点赞数
文章标签： 运维 数据库 java

技术提示65显示了如何在两个单独的容器中使用WildFly和MySQL运行Java EE 7应用程序。 它需要显式启动两个容器，并使用--link链接它们。 定义和控制多容器服务是一种常见的设计模式，目的是使应用程序正常运行。

认识Fig – Docker Orchestration工具。

图允许：

  • 在一个配置文件中定义多个容器
  • 通过在两个容器之间创建链接来创建它们之间的依赖关系
  • 以正确的顺序启动容器

让我们开始吧！

  1. 安装图为： 
    curl -L https://github.com/docker/fig/releases/download/1.0.1/fig-`uname-s`-`uname -m` > /usr/local/bin/fig; chmod +x /usr/local/bin/fig
  2. 图的入口是一个配置文件，它定义了容器及其依赖性。 技术提示65中的等效配置文件为： 
    mysqldb:
  image: mysql:latest
  environment:
    MYSQL_DATABASE: sample
    MYSQL_USER: mysql
    MYSQL_PASSWORD: mysql
    MYSQL_ROOT_PASSWORD: supersecret
mywildfly:
  image: arungupta/wildfly-mysql-javaee7
  links:
    - mysqldb:db
  ports:
    - 8080:8080

    此基于YML的配置文件具有：

    1. 由名称“ mysqldb”和“ mywildfly”定义的两个容器
    2. 图像名称使用“图像”定义
    3. MySQL容器的环境变量在“环境”中定义
    4. MySQL容器通过“链接”与WildFly容器链接
    5. 使用“端口”实现端口转发
  3. 可以通过以下命令以分离模式启动所有容器： 
    fig up -d

    输出显示为： 

    Creating wildflymysqljavaee7_mysqldb_1...
Creating wildflymysqljavaee7_mywildfly_1...

    图命令允许监视和更新容器的状态：

    1. 日志可以看成是： 
      fig logs
    2. 发出以下命令可以查看容器状态： 
      fig ps

      将输出显示为： 

      Name                            Command               State                Ports               
----------------------------------------------------------------------------------------------
wildflymysqljavaee7_mysqldb_1     /entrypoint.sh mysqld --da ...   Up      3306/tcp                         
wildflymysqljavaee7_mywildfly_1   /opt/jboss/wildfly/customi ...   Up      0.0.0.0:8080->8080/tcp, 9990/tcp
    3. 可以通过以下方式停止容器： 
      fig stop
    4. 或者，可以通过以下命令在前台启动容器： 
      fig up

      输出显示为： 

      wildfly-mysql-javaee7> fig up
Creating wildflymysqljavaee7_mysqldb_1...
Creating wildflymysqljavaee7_mywildfly_1...
Attaching to wildflymysqljavaee7_mysqldb_1, wildflymysqljavaee7_mywildfly_1
mywildfly_1 | => Starting WildFly server
mywildfly_1 | => Waiting for the server to boot
mysqldb_1   | 2014-12-23 18:28:10 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Using atomics to ref count buffer pool pages
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: The InnoDB memory heap is disabled
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Memory barrier is not used
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Compressed tables use zlib 1.2.3
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Using Linux native AIO
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Not using CPU crc32 instructions
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Initializing buffer pool, size = 128.0M
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Completed initialization of buffer pool
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Database physically writes the file full: wait...
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
mysqldb_1   | 2014-12-23 18:28:10 12 [Warning] InnoDB: New log files created, LSN=45781
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Doublewrite buffer not found: creating new
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Doublewrite buffer created
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: 128 rollback segment(s) are active.
mysqldb_1   | 2014-12-23 18:28:10 12 [Warning] InnoDB: Creating foreign key constraint system tables.
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Foreign key constraint system tables created
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Creating tablespace and datafile system tables.
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Tablespace and datafile system tables created.
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Waiting for purge to start
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: 5.6.22 started; log sequence number 0
mywildfly_1 | =========================================================================
mywildfly_1 | 
mywildfly_1 |   JBoss Bootstrap Environment
mywildfly_1 | 
mywildfly_1 |   JBOSS_HOME: /opt/jboss/wildfly
mywildfly_1 | 
mywildfly_1 |   JAVA: /usr/lib/jvm/java/bin/java
mywildfly_1 | 
mywildfly_1 |   JAVA_OPTS:  -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
mywildfly_1 | 
mywildfly_1 | =========================================================================
mywildfly_1 | 
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] Binlog end
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: FTS optimize thread exiting.
mysqldb_1   | 2014-12-23 18:28:10 12 [Note] InnoDB: Starting shutdown...
mywildfly_1 | 18:28:11,257 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
mywildfly_1 | 18:28:11,543 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
mywildfly_1 | 18:28:11,631 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: WildFly 8.2.0.Final "Tweek" starting
mysqldb_1   | 2014-12-23 18:28:12 12 [Note] InnoDB: Shutdown completed; log sequence number 1625977
mywildfly_1 | 18:28:12,621 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
mywildfly_1 | 18:28:12,642 INFO  [org.xnio] (MSC service thread 1-10) XNIO version 3.3.0.Final
mywildfly_1 | 18:28:12,652 INFO  [org.xnio.nio] (MSC service thread 1-10) XNIO NIO Implementation Version 3.3.0.Final
mywildfly_1 | 18:28:12,697 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) JBAS010280: Activating Infinispan subsystem.
mywildfly_1 | 18:28:12,698 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 31) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors
mywildfly_1 | 18:28:12,880 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
mywildfly_1 | 18:28:12,917 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 40) JBAS011800: Activating Naming Subsystem
mywildfly_1 | 18:28:12,987 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 46) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
mywildfly_1 | 18:28:13,002 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 45) JBAS013171: Activating Security Subsystem
mywildfly_1 | 18:28:13,082 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-7) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.9.Final)
mywildfly_1 | 18:28:13,084 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 38) JBAS012615: Activated the following JSF Implementations: [main]
mywildfly_1 | 18:28:13,088 INFO  [org.jboss.as.security] (MSC service thread 1-15) JBAS013170: Current PicketBox version=4.0.21.Final
mywildfly_1 | 18:28:13,097 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017502: Undertow 1.1.0.Final starting
mywildfly_1 | 18:28:13,098 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017502: Undertow 1.1.0.Final starting
mywildfly_1 | 18:28:13,109 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) JBAS010417: Started Driver service with driver-name = h2
mywildfly_1 | 18:28:13,132 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
mywildfly_1 | 18:28:13,355 INFO  [org.jboss.remoting] (MSC service thread 1-10) JBoss Remoting version 4.0.6.Final
mywildfly_1 | 18:28:13,502 INFO  [org.jboss.as.naming] (MSC service thread 1-13) JBAS011802: Starting Naming Service
mywildfly_1 | 18:28:13,503 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session 
mysqldb_1   | OK
mysqldb_1   | 
mywildfly_1 | 18:28:14,161 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017527: Creating file handler for path /opt/jboss/wildfly/welcome-content
mysqldb_1   | Filling help tables...2014-12-23 18:28:14 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysqldb_1   | 2014-12-23 18:28:14 35 [Note] InnoDB: Using atomics to ref count buffer pool pages
mysqldb_1   | 2014-12-23 18:28:14 35 [Note] InnoDB: The InnoDB memory heap is disabled
mysqldb_1   | 2014-12-23 18:28:14 35 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysqldb_1   | 2014-12-23 18:28:14 35 [Note] InnoDB: Memory barrier is not used
mysqldb_1   | 2014-12-23 18:28:14 35 [Note] InnoDB: Compressed tables use zlib 1.2.3
mysqldb_1   | 2014-12-23 18:28:14 35 [Note] InnoDB: Using Linux native AIO
mysqldb_1   | 2014-12-23 18:28:14 35 [Note] InnoDB: Not using CPU crc32 instructions
mysqldb_1   | 2014-12-23 18:28:14 35 [Note] InnoDB: Initializing buffer pool, size = 128.0M
mywildfly_1 | 18:28:14,190 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-9) JBAS017525: Started server default-server.
mysqldb_1   | 2014-12-23 18:28:14 35 [Note] InnoDB: Completed initialization of buffer pool
mysqldb_1   | 2014-12-23 18:28:14 35 [Note] InnoDB: Highest supported file format is Barracuda.
mysqldb_1   | 2014-12-23 18:28:14 35 [Note] InnoDB: 128 rollback segment(s) are active.
mysqldb_1   | 2014-12-23 18:28:14 35 [Note] InnoDB: Waiting for purge to start
mywildfly_1 | 18:28:14,271 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-16) JBAS017531: Host default-host starting
mysqldb_1   | 2014-12-23 18:28:14 35 [Note] InnoDB: 5.6.22 started; log sequence number 1625977
mywildfly_1 | 18:28:14,366 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-9) JBAS017519: Undertow HTTP listener default listening on /0.0.0.0:8080
mysqldb_1   | 2014-12-23 18:28:14 35 [Note] Binlog end
mysqldb_1   | 2014-12-23 18:28:14 35 [Note] InnoDB: FTS optimize thread exiting.
mysqldb_1   | 2014-12-23 18:28:14 35 [Note] InnoDB: Starting shutdown...
mywildfly_1 | 18:28:14,548 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) JBAS015012: Started FileSystemDeploymentService for directory /opt/jboss/wildfly/standalone/deployments
mywildfly_1 | 18:28:14,584 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-14) JBAS010400: Bound data source 
mywildfly_1 | 18:28:14,697 INFO  [org.jboss.ws.common.management] (MSC service thread 1-15) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final
mywildfly_1 | 18:28:14,766 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
mywildfly_1 | 18:28:14,766 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
mywildfly_1 | 18:28:14,768 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 3852ms - Started 184 of 234 services (82 services are lazy, passive or on-demand)
mywildfly_1 | => Executing the commands
mywildfly_1 | => MYSQL_HOST: 
mywildfly_1 | => MYSQL_PORT: 
mywildfly_1 | => MYSQL (host):  172.17.0.4
mywildfly_1 | => MYSQL (port):  3306
mysqldb_1   | 2014-12-23 18:28:16 35 [Note] InnoDB: Shutdown completed; log sequence number 1625987
mywildfly_1 | [standalone@localhost:9990 /] batch
mywildfly_1 | [standalone@localhost:9990 / #] 
mywildfly_1 | [standalone@localhost:9990 / #] # Add MySQL module
mywildfly_1 | [standalone@localhost:9990 / #] module add --name=com.mysql --resources=/opt/jboss/wildfly/customization/mysql-connector-java-5.1.31-bin.jar --dependencies=javax.api,javax.transaction.api
mywildfly_1 | [standalone@localhost:9990 / #] 
mywildfly_1 | [standalone@localhost:9990 / #] # Add MySQL driver
mywildfly_1 | [standalone@localhost:9990 / #] /subsystem=datasources/jdbc-driver=mysql:add(driver-name=mysql,driver-module-name=com.mysql,driver-xa-datasource-class-name=com.mysql.jdbc.jdbc2.optional.MysqlXADataSource)
mywildfly_1 | [standalone@localhost:9990 / #] 
mywildfly_1 | [standalone@localhost:9990 / #] # Add the datasource
mywildfly_1 | [standalone@localhost:9990 / #] #data-source add --name=mysqlDS --driver-name=mysql --jndi-name=java:jboss/datasources/ExampleMySQLDS --connection-url=jdbc:mysql://:/sample?useUnicode=true&characterEncoding=UTF-8 --user-name=mysql --password=mysql --use-ccm=false --max-pool-size=25 --blocking-timeout-wait-millis=5000 --enabled=true
mywildfly_1 | [standalone@localhost:9990 / #] 
mywildfly_1 | [standalone@localhost:9990 / #] data-source add --name=mysqlDS --driver-name=mysql --jndi-name=java:jboss/datasources/ExampleMySQLDS --connection-url=jdbc:mysql://172.17.0.4:3306/sample?useUnicode=true&characterEncoding=UTF-8 --user-name=mysql --password=mysql --use-ccm=false --max-pool-size=25 --blocking-timeout-wait-millis=5000 --enabled=true
mywildfly_1 | [standalone@localhost:9990 / #] 
mywildfly_1 | [standalone@localhost:9990 / #] # Execute the batch
mywildfly_1 | [standalone@localhost:9990 / #] run-batch
mywildfly_1 | 18:28:16,957 INFO  [org.jboss.as.connector.subsystems.datasources] (management-handler-thread - 4) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
mywildfly_1 | 18:28:16,963 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-11) JBAS010417: Started Driver service with driver-name = mysql
mywildfly_1 | 18:28:16,976 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010400: Bound data source 
mywildfly_1 | The batch executed successfully
mywildfly_1 | [standalone@localhost:9990 /] 
mywildfly_1 | => Shutting down WildFly
mysqldb_1   | OK
mysqldb_1   | 
mysqldb_1   | To start mysqld at boot time you have to copy
mysqldb_1   | support-files/mysql.server to the right place for your system
mysqldb_1   | 
mysqldb_1   | PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
mysqldb_1   | To do so, start the server, then issue the following commands:
mysqldb_1   | 
mysqldb_1   |   ./bin/mysqladmin -u root password 'new-password'
mysqldb_1   |   ./bin/mysqladmin -u root -h 8aca3b20ca40 password 'new-password'
mysqldb_1   | 
mysqldb_1   | Alternatively you can run:
mysqldb_1   | 
mysqldb_1   |   ./bin/mysql_secure_installation
mysqldb_1   | 
mysqldb_1   | which will also give you the option of removing the test
mysqldb_1   | databases and anonymous user created by default.  This is
mysqldb_1   | strongly recommended for production servers.
mysqldb_1   | 
mysqldb_1   | See the manual for more instructions.
mysqldb_1   | 
mysqldb_1   | You can start the MySQL daemon with:
mysqldb_1   | 
mysqldb_1   |   cd . ; ./bin/mysqld_safe &
mysqldb_1   | 
mysqldb_1   | You can test the MySQL daemon with mysql-test-run.pl
mysqldb_1   | 
mysqldb_1   |   cd mysql-test ; perl mysql-test-run.pl
mysqldb_1   | 
mysqldb_1   | Please report any problems at http://bugs.mysql.com/
mysqldb_1   | 
mysqldb_1   | The latest information about MySQL is available on the web at
mysqldb_1   | 
mysqldb_1   |   http://www.mysql.com
mysqldb_1   | 
mysqldb_1   | Support MySQL by buying support/licenses at http://shop.mysql.com
mysqldb_1   | 
mysqldb_1   | New default config file was created as ./my.cnf and
mysqldb_1   | will be used by default by the server when you start it.
mysqldb_1   | You may edit this file to change server settings
mysqldb_1   | 
mysqldb_1   | 2014-12-23 18:28:17 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] Plugin 'FEDERATED' is disabled.
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] InnoDB: Using atomics to ref count buffer pool pages
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] InnoDB: The InnoDB memory heap is disabled
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] InnoDB: Memory barrier is not used
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] InnoDB: Compressed tables use zlib 1.2.3
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] InnoDB: Using Linux native AIO
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] InnoDB: Not using CPU crc32 instructions
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] InnoDB: Initializing buffer pool, size = 128.0M
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] InnoDB: Completed initialization of buffer pool
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] InnoDB: Highest supported file format is Barracuda.
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] InnoDB: 128 rollback segment(s) are active.
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] InnoDB: Waiting for purge to start
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] InnoDB: 5.6.22 started; log sequence number 1625987
mysqldb_1   | 2014-12-23 18:28:17 1 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 76e25b07-8ad1-11e4-9167-0242ac110004.
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] Server hostname (bind-address): '*'; port: 3306
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] IPv6 is available.
mysqldb_1   | 2014-12-23 18:28:17 1 [Note]   - '::' resolves to '::';
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] Server socket created on IP: '::'.
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] Event Scheduler: Loaded 0 events
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] Execution of init_file '/tmp/mysql-first-time.sql' started.
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] Execution of init_file '/tmp/mysql-first-time.sql' ended.
mysqldb_1   | 2014-12-23 18:28:17 1 [Note] mysqld: ready for connections.
mysqldb_1   | Version: '5.6.22'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Server (GPL)
mywildfly_1 | {"outcome" => "success"}
mywildfly_1 | => Restarting WildFly
mywildfly_1 | 18:28:17,931 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-15) JBAS010409: Unbound data source 
mywildfly_1 | 18:28:17,931 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-11) JBAS010409: Unbound data source 
mywildfly_1 | 18:28:17,942 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) JBAS017532: Host default-host stopping
mywildfly_1 | 18:28:17,946 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-11) JBAS010418: Stopped Driver service with driver-name = mysql
mywildfly_1 | 18:28:17,956 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) JBAS010418: Stopped Driver service with driver-name = h2
mywildfly_1 | 18:28:17,981 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017521: Undertow HTTP listener default suspending
mywildfly_1 | 18:28:18,004 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017520: Undertow HTTP listener default stopped, was bound to /0.0.0.0:8080
mywildfly_1 | 18:28:18,007 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) JBAS017506: Undertow 1.1.0.Final stopping
mywildfly_1 | =========================================================================
mywildfly_1 | 
mywildfly_1 |   JBoss Bootstrap Environment
mywildfly_1 | 
mywildfly_1 |   JBOSS_HOME: /opt/jboss/wildfly
mywildfly_1 | 
mywildfly_1 |   JAVA: /usr/lib/jvm/java/bin/java
mywildfly_1 | 
mywildfly_1 |   JAVA_OPTS:  -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
mywildfly_1 | 
mywildfly_1 | =========================================================================
mywildfly_1 | 
mywildfly_1 | 18:28:18,082 INFO  [org.jboss.as] (MSC service thread 1-10) JBAS015950: WildFly 8.2.0.Final "Tweek" stopped in 148ms
mywildfly_1 | 18:28:18,438 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
mywildfly_1 | 18:28:18,691 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
mywildfly_1 | 18:28:18,769 INFO  [org.jboss.as] (MSC service thread 1-7) JBAS015899: WildFly 8.2.0.Final "Tweek" starting
mywildfly_1 | 18:28:19,737 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
mywildfly_1 | 18:28:19,756 INFO  [org.xnio] (MSC service thread 1-12) XNIO version 3.3.0.Final
mywildfly_1 | 18:28:19,765 INFO  [org.xnio.nio] (MSC service thread 1-12) XNIO NIO Implementation Version 3.3.0.Final
mywildfly_1 | 18:28:19,798 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) JBAS010280: Activating Infinispan subsystem.
mywildfly_1 | 18:28:19,802 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 31) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors
mywildfly_1 | 18:28:19,834 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 40) JBAS011800: Activating Naming Subsystem
mywildfly_1 | 18:28:19,837 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 45) JBAS013171: Activating Security Subsystem
mywildfly_1 | 18:28:19,843 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 46) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
mywildfly_1 | 18:28:19,846 INFO  [org.jboss.as.security] (MSC service thread 1-9) JBAS013170: Current PicketBox version=4.0.21.Final
mywildfly_1 | 18:28:19,868 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 38) JBAS012615: Activated the following JSF Implementations: [main]
mywildfly_1 | 18:28:19,892 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-10) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.9.Final)
mywildfly_1 | 18:28:19,902 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
mywildfly_1 | 18:28:19,943 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017502: Undertow 1.1.0.Final starting
mywildfly_1 | 18:28:19,943 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-15) JBAS017502: Undertow 1.1.0.Final starting
mywildfly_1 | 18:28:19,969 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
mywildfly_1 | 18:28:19,980 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) JBAS010417: Started Driver service with driver-name = h2
mywildfly_1 | 18:28:20,027 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session 
mywildfly_1 | 18:28:20,027 INFO  [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
mywildfly_1 | 18:28:20,139 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
mywildfly_1 | 18:28:20,141 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-13) JBAS010417: Started Driver service with driver-name = mysql
mywildfly_1 | 18:28:20,155 INFO  [org.jboss.remoting] (MSC service thread 1-12) JBoss Remoting version 4.0.6.Final
mywildfly_1 | 18:28:20,391 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017527: Creating file handler for path /opt/jboss/wildfly/welcome-content
mywildfly_1 | 18:28:20,408 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-14) JBAS017525: Started server default-server.
mywildfly_1 | 18:28:20,429 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-14) JBAS017531: Host default-host starting
mywildfly_1 | 18:28:20,560 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017519: Undertow HTTP listener default listening on /0.0.0.0:8080
mywildfly_1 | 18:28:20,696 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-13) JBAS015012: Started FileSystemDeploymentService for directory /opt/jboss/wildfly/standalone/deployments
mywildfly_1 | 18:28:20,697 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-16) JBAS015876: Starting deployment of "temp.war" (runtime-name: "temp.war")
mywildfly_1 | 18:28:20,701 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015876: Starting deployment of "employees.war" (runtime-name: "employees.war")
mywildfly_1 | 18:28:20,719 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source 
mywildfly_1 | 18:28:20,720 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source 
mywildfly_1 | 18:28:20,815 INFO  [org.jboss.as.jpa] (MSC service thread 1-6) JBAS011401: Read persistence.xml for MyPU
mywildfly_1 | 18:28:20,867 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 50) JBAS011409: Starting Persistence Unit (phase 1 of 2) Service 'employees.war#MyPU'
mywildfly_1 | 18:28:20,880 INFO  [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 50) HHH000204: Processing PersistenceUnitInfo [
mywildfly_1 | 	name: MyPU
mywildfly_1 | 	...]
mywildfly_1 | 18:28:20,959 INFO  [org.jboss.ws.common.management] (MSC service thread 1-10) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final
mywildfly_1 | 18:28:20,980 INFO  [org.hibernate.Version] (ServerService Thread Pool -- 50) HHH000412: Hibernate Core {4.3.7.Final}
mywildfly_1 | 18:28:20,984 INFO  [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 50) HHH000206: hibernate.properties not found
mywildfly_1 | 18:28:20,986 INFO  [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 50) HHH000021: Bytecode provider name : javassist
mywildfly_1 | 18:28:21,081 INFO  [org.jboss.weld.deployer] (MSC service thread 1-9) JBAS016002: Processing weld deployment employees.war
mywildfly_1 | 18:28:21,127 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-9) HV000001: Hibernate Validator 5.1.3.Final
mywildfly_1 | 18:28:21,180 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: /temp
mywildfly_1 | 18:28:21,264 INFO  [org.jboss.weld.deployer] (MSC service thread 1-13) JBAS016005: Starting Services for CDI deployment: employees.war
mywildfly_1 | 18:28:21,298 INFO  [org.jboss.weld.Version] (MSC service thread 1-13) WELD-000900: 2.2.6 (Final)
mywildfly_1 | 18:28:21,310 INFO  [org.jboss.weld.deployer] (MSC service thread 1-10) JBAS016008: Starting weld service for deployment employees.war
mywildfly_1 | 18:28:21,452 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 50) JBAS011409: Starting Persistence Unit (phase 2 of 2) Service 'employees.war#MyPU'
mywildfly_1 | 18:28:21,521 INFO  [org.hibernate.annotations.common.Version] (ServerService Thread Pool -- 50) HCANN000001: Hibernate Commons Annotations {4.0.4.Final}
mysqldb_1   | 2014-12-23 18:28:21 1 [Warning] IP address '172.17.0.5' could not be resolved: Name or service not known
mywildfly_1 | 18:28:21,845 INFO  [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 50) HHH000400: Using dialect: org.hibernate.dialect.MySQL5Dialect
mywildfly_1 | 18:28:21,940 INFO  [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory
mywildfly_1 | 18:28:22,276 INFO  [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 50) HHH000400: Using dialect: org.hibernate.dialect.MySQL5Dialect
mywildfly_1 | 18:28:22,282 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: drop table if exists EMPLOYEE_SCHEMA
mywildfly_1 | 18:28:22,289 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: drop table if exists hibernate_sequence
mywildfly_1 | 18:28:22,290 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: create table EMPLOYEE_SCHEMA (id integer not null, name varchar(40), primary key (id))
mywildfly_1 | 18:28:22,300 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: create table hibernate_sequence ( next_val bigint )
mywildfly_1 | 18:28:22,310 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: insert into hibernate_sequence values ( 1 )
mywildfly_1 | 18:28:22,312 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (1, 'Penny')
mywildfly_1 | 18:28:22,314 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (2, 'Sheldon')
mywildfly_1 | 18:28:22,317 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (3, 'Amy')
mywildfly_1 | 18:28:22,320 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (4, 'Leonard')
mywildfly_1 | 18:28:22,323 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (5, 'Bernadette')
mywildfly_1 | 18:28:22,324 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (6, 'Raj')
mywildfly_1 | 18:28:22,328 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (7, 'Howard')
mywildfly_1 | 18:28:22,330 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (8, 'Priya')
mywildfly_1 | 18:28:23,361 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Deploying javax.ws.rs.core.Application: class org.javaee7.samples.employees.MyApplication
mywildfly_1 | 18:28:23,396 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017534: Registered web context: /employees
mywildfly_1 | 18:28:23,433 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "employees.war" (runtime-name : "employees.war")
mywildfly_1 | 18:28:23,434 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "temp.war" (runtime-name : "temp.war")
mywildfly_1 | 18:28:23,452 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
mywildfly_1 | 18:28:23,453 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
mywildfly_1 | 18:28:23,453 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 5330ms - Started 344 of 404 services (102 services are lazy, passive or on-demand)
mywildfly_1 | 18:28:30,954 INFO  [stdout] (default task-1) Hibernate: select employee0_.id as id1_0_, employee0_.name as name2_0_ from EMPLOYEE_SCHEMA employee0_
    5. 使用boot2docker ip找出IP地址并以以下方式访问该应用程序： 
      curl http://192.168.59.103:8080/employees/resources/employees
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><collection><employee><id>1</id><name>Penny</name></employee><employee><id>2</id><name>Sheldon</name></employee><employee><id>3</id><name>Amy</name></employee><employee><id>4</id><name>Leonard</name></employee><employee><id>5</id><name>Bernadette</name></employee><employee><id>6</id><name>Raj</name></employee><employee><id>7</id><name>Howard</name></employee><employee><id>8</id><name>Priya</name></employee></collection>

    键入fig可以看到Fig命令的完整列表： 

    Commands:
  build     Build or rebuild services
  help      Get help on a command
  kill      Kill containers
  logs      View output from containers
  port      Print the public port for a port binding
  ps        List containers
  pull      Pulls service images
  rm        Remove stopped containers
  run       Run a one-off command
  scale     Set number of containers for a service
  start     Start services
  stop      Stop services
  restart   Restart services
  up        Create and start containers

    scale命令特别有趣，我们将在后续博客中对其进行介绍。

    github上的文件问题。

    请享用！

翻译自: https://www.javacodegeeks.com/2015/01/docker-orchestration-using-fig.html

danpob13624
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Docker的fig简介
wjianwei666的专栏
12-28 524
以上的内容首先告诉 Docker 在容器里面安装 Python ，代码的路径还有Python 依赖包。这个实验假设你已经知道一些 Python 知识，如果你不熟悉，但清楚概念上的东西也是没有问题的。这个 web 应用已经开始在你的 docker 守护进程里面监听着 5000 端口了（如果你有使用 boot2docker ，执行。，这是一个能够让 Redis 上的一个值自增的简单 web 应用，基于 Flask 框架。，然后 Fig 就会启动并运行你的应用了。如果你想要在后台运行你的服务，可以在执行。
深入浅出Docker（五）：基于Fig搭建开发环境
dodott的专栏
11-21 734
【编者按】Docker是PaaS供应商dotCloud开源的一个基于LXC 的高级容器引擎，源代码托管在 GitHub 上, 基于Go语言开发并遵从Apache 2.0协议开源。Docker提供了一种在安全、可重复的环境中自动部署软件的方式，它的出现拉开了基于云计算平台发布产品方式的变革序幕。为了更好的促进Docker在国内的发展以及传播，我们决定开设《深入浅出Docker》专栏，邀请Docker
Docker 编排工具 Fig 介绍
weixin_34162629的博客
05-02 127
Docker 编排工具 Fig 介绍 【编者的话】Fig是一个基于Docker的用于快速搭建开发环境的工具，目前Fig团队已经加入Docker公司。Fig通过一个配置文件来管理多个 Docker容器，非常适合组合使用多个容器进行开发的场景。Fig可以和Docker一起来构建基于Docker的复杂应用。本文详细介绍了Fig的安装以及使用。 什么是编排？...
Docker的fig
2301_76599986的博客
05-12 82
在你的应用里面添加一个fig.yml文件，并指定一些简单的内容，执行fig up它就能帮你快速建立起一个容器。
Docker实践3：fig搭建mediawiki
modabobo
02-05 170
fig，无花果。fig项目源自docker，可以认为是快速搭建基于Docker的隔离开发环境的工具。 一、安装fig $ mkdir docker; cd docker $ curl -L https://github.com/docker/fig/releases/download/1.0.1/fig-`uname -s`-`uname -m` &gt; fig $ sudo chmod +...
Docker结合自动化编排工具Fig的使用方法-电脑资料.pdf
11-24
在本文中，我们将深入探讨Docker结合自动化编排工具Fig的使用方法。Docker是一个流行的开源平台，它允许开发者打包他们的应用及其依赖环境到一个可移植的容器中，从而实现跨平台的无缝部署。而Fig，作为Docker的配套...
Docker 容器编排利器Compose（起步篇）
01-20
Compose的前身是Fig，Fig被Docker收购之后正式更名为Compose，Compose向下兼容Fig。Compose是一个用于定义和运行多容器Docker应用的工具，只需要一个Compose的配置文件和一个简单的命令就可以创建并运行应用所需的...
Docker结合自动化编排工具Fig的使用方法-电脑资料.docx
11-24
。。。
gig:gig是一个受图启发的简单docker编排工具
05-14
配置格式很简单，并在docker run命令的选项上使用。 有关格式的详细说明，请参见上文。 webserver : image : nginx ports : - " 80:80 " - " 443:443 " volumes : - ./my_web_root:/usr/share/nginx/html ...
Docker编排工具Fig介绍
weixin_34049032的博客
09-04 121
本文讲的是Docker编排工具Fig介绍，【编者的话】Fig是一个基于Docker的用于快速搭建开发环境的工具，目前Fig团队已经加入Docker公司。Fig通过一个配置文件来管理多个Docker容器，非常适合组合使用多个容器进行开发的场景。Fig可以和Docker一起来构建基于Docker的复杂应用。本文详细介绍了Fig的安装以及使用。 什么是编...
Docker 实战：Docker的fig简介
qq_33240556的博客
03-17 191
通过一个配置文件，可以快速创建和管理多个相互依赖的服务容器，例如数据库、Web服务器、缓存服务等。服务，它监听宿主机的 8000 端口并将请求转发到容器内的 8000 端口，同时它依赖于。文件确保了环境的一致性和可复现性，任何团队成员都可以根据该文件来重现相同的应用部署环境。），开发者可以轻松地配置服务、网络和数据卷等，并一次性启动整个应用的所有相关组件。：可以定义容器间的数据卷共享，以及网络通信方式，如是否在同一桥接网络内进行通信。：自动处理容器之间的依赖关系，按照正确顺序启动和停止容器。
Docker Compose容器编排
Shadow__Flow的博客
11-30 306
一、Docker Compose简介 Compose项目是Docker官方的开源项目，负责实现对Docker容器集群的快速编排。它是一个定义和运行多容器的docker应用工具。使用compose，你能通过YMAL文件配置你自己的服务，然后通过一个命令，你能使用配置文件创建和运行所有的服务。 Compose是一个定位“定义和运行多个Docker容器应用的工具”，其前身是Fig，目前使用的Compose仍然兼容Fig格式的模板文件。 Compose的代码主要使用Python编写，其开源地址为：https://g
【docker】fig开源项目
one_clouder的专栏
09-05 827
今天分析fig开源项目。
docker fig mysql_docker管理工具 Fig 配置文件fig.yml的详解
weixin_39922929的博客
01-19 110
fig.yml使用fig.yml更方便的定义 docker服务 和操作使用docker。你不必再为docker复杂的命令和配置发愁image指定要使用的imageimage: ubuntuimage: orchardup/postgresqlimage: a4bc65fdbuilddocker file的所在目录指定build: /path/to/build/dircommand重写默认执行的命令...
Docker 实战：Docker中Fig命令参考
最新发布
qq_33240556的博客
03-18 457
Fig 是一个早期的容器编排工具，后来被 Docker 公司收购并发展为现在的 Docker Compose。如果你是在寻找 Docker Compose 相关的命令参考，请看以下基本的。记得在使用这些命令前，确保在项目目录下有一个有效的。文件，该文件定义了服务、网络以及数据卷等配置信息。命令在 Docker 中已经被。
Docker学习笔记七 使用Fig编配Docker
weixin_33884611的博客
07-14 120
2019独角兽企业重金招聘Python工程师标准>>> ...
docker容器使用--net=host获取容器IP,报错VM-XX:Name or Service not known
小兀的博客
06-01 5883
目录标题1. 背景和问题背景问题问题查找 1. 背景和问题 背景 项目使用了Nacos微服务架构，由于项目运行需要启动注册中心、网关、认证中心、分布式事务中心等多个微服务，非常占用物理机内存和CPU，所以部署了一个开发服务器，把这些服务运行在服务器上，我只需要运行自己正在开发的的服务模块就可以，这样开发用的物理机一下就释放了很多内存，开发起来更顺畅。 问题 但是问题来了，docker容器自动分配的ip为172.17.0.0/24网段的ip，开发用的物理机和这个容器不在一个网段，根本没法访问到，这时候网上查到
为什么要用Fig来实现Docker自动化？
weixin_34161029的博客
09-13 95
本文讲的是为什么要用Fig来实现Docker自动化，【编者的话】本文主要讲解了如何用Fig来解决Docker多参数启动容器的问题（Fig入门可以参照这里）以及使用Fig需要注意的一些事项，亮点是文末介绍了Fig的一些缺陷与不足，同时作者认为Fig在测试场景中同样适用。 如果你正在使用Docker，但还没有尝试过Fig，那这篇文章正适合你。你可能像我...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值