Docker deployment document (2)

The project package will be mounted separately, and the running environment will still be mirrored.

1. Etlloaderdocker run-d-restart=always\-net huoshu-ip 172.21.1.4-p 8380 ORACLE_ADDR=172.16.4.101 8380\-e ORACLE_ADDR=172.16.4.101\-v / opt/apps/etlloader:/opt/etlloader\-v / var/log/etlloader:/opt/etlloader/consolelog\ reg01.sky-mobi.com/huoshu/etlloader-separate:1.0.0

Directory structure of / opt/apps/etlloader

. ├── exe.jar ├── exe.sh ├── run.jar └── run.sh2. Tomcat project

Since the access path under the webapps directory is different from the name of the project package, you need to extract the war package in advance instead of automatically decompressing it when tomcat starts.

... There may not be a jdk on the host machine. The jar command cannot be used, so you'd better upload it as a tar package.

Hdc-manager

The war package is decompressed and placed in the / opt/apps directory, that is, the full path of the project is / opt/apps/hdc-manager

Docker run-d-- restart=always\-- net huoshu-- ip=172.21.1.2-p 8180 purl 8080\-v / opt/apps/hdc-manager:/usr/local/apache-tomcat-8.5.4/webapps/se\-v / var/log/hdc-manager:/usr/local/apache-tomcat-8.5.4/logs\-e ORACLE_ADDR=172.16.4.101\ reg01.sky-mobi.com/huoshu/tomcat:latest

Skydata-se

The war package is decompressed and placed in the / opt/apps directory, that is, the full path of the project is / opt/apps/skydata-se

Docker run-d-- restart=always\-- net huoshu-- ip=172.21.1.3-p 8280 purl 8080\-v / opt/apps/skydata-se:/usr/local/apache-tomcat-8.5.4/webapps/skydata\-v / var/log/skydata-se:/usr/local/apache-tomcat-8.5.4/logs\-e ORACLE_ADDR=172.16.4.101\ reg01.sky-mobi.com/huoshu/tomcat:latest

The members of the final / opt/apps directory are as follows

Front ├── bi_FE ├── hdc_FE └── nginx.conf.d ├── bi.conf └── hdc.confhdc-manager ├── index.jsp ├── META-INF └── WEB-INFskydata-se ├── index.jsp ├── execl ├── META-INF └── WEB-INFetlloader ├── exe.jar ├── exe. Sh ├── run.jar └── run.sh