欢迎您访问程序员文章站本站旨在为大家提供分享程序员计算机编程知识！
您现在的位置是： 首页

Linux上搭建meterSphere

程序员文章站 2022-05-21 23:34:31
...

镜像下载、域名解析、时间同步请点击 阿里云开源镜像站

一、安装Docker

（1）安装CentOS Docker

  1. curl -fsSL https://get.docker.com | bash -s docker --mirror Aliyun

执行后效果：

    

  1. [root@localhost base]# curl -fsSL https://get.docker.com | bash -s docker --mirror Aliyun
    2. 

  2. # Executing docker install script, commit: 93d2499759296ac1f9c510605fef85052a2c32be
    3. 

  3. Warning: the "docker" command appears to already exist on this system.
    4. 

    5. 

  5. If you already have Docker installed, this script can cause trouble, which is
    6. 

  6. why we're displaying this warning and provide the opportunity to cancel the
    7. 

  7. installation.
    8. 

    9. 

  9. If you installed the current Docker package using this script and are using it
    10. 

  10. again to update Docker, you can safely ignore this message.
    11. 

    12. 

  12. You may press Ctrl+C now to abort this script.
    13. 

  13. + sleep 20
    14. 

  14. + sh -c 'yum install -y -q yum-utils'
    15. 

  15. Package yum-utils-1.1.31-54.el7_8.noarch already installed and latest version
    16. 

  16. + sh -c 'yum-config-manager --add-repo https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo'
    17. 

  17. Loaded plugins: fastestmirror, langpacks
    18. 

  18. adding repo from: https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
    19. 

  19. grabbing file https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo to /etc/yum.repos.d/docker-ce.repo
    20. 

  20. repo saved to /etc/yum.repos.d/docker-ce.repo
    21. 

  21. + '[' stable '!=' stable ']'
    22. 

  22. + sh -c 'yum makecache'
    23. 

  23. Loaded plugins: fastestmirror, langpacks
    24. 

  24. base                                                                                                                                                                 | 3.6 kB  00:00:00
    25. 

  25. docker-ce-stable                                                                                                                                                     | 3.5 kB  00:00:00
    26. 

  26. extras                                                                                                                                                               | 2.9 kB  00:00:00
    27. 

  27. updates                                                                                                                                                              | 2.9 kB  00:00:00
    28. 

  28. Loading mirror speeds from cached hostfile
    29. 

  29.  * base: mirrors.aliyun.com
    30. 

  30.  * extras: mirrors.aliyun.com
    31. 

  31.  * updates: mirrors.aliyun.com
    32. 

  32. Metadata Cache Created
    33. 

  33. + '[' -n '' ']'
    34. 

  34. + sh -c 'yum install -y -q docker-ce'
    35. 

  35. + version_gte 20.10
    36. 

  36. + '[' -z '' ']'
    37. 

  37. + return 0
    38. 

  38. + sh -c 'yum install -y -q docker-ce-rootless-extras'
    39. 

  39. Package docker-ce-rootless-extras-20.10.12-3.el7.x86_64 already installed and latest version
    40. 

    41. 

  41. ================================================================================
    42. 

    43. 

  43. To run Docker as a non-privileged user, consider setting up the
    44. 

  44. Docker daemon in rootless mode for your user:
    45. 

    46. 

  46.     dockerd-rootless-setuptool.sh install
    47. 

    48. 

  48. Visit https://docs.docker.com/go/rootless/ to learn about rootless mode.
    49. 

    50. 

    51. 

  51. To run the Docker daemon as a fully privileged service, but granting non-root
    52. 

  52. users access, refer to https://docs.docker.com/go/daemon-access/
    53. 

    54. 

  54. WARNING: Access to the remote API on a privileged Docker daemon is equivalent
    55. 

  55.          to root access on the host. Refer to the 'Docker daemon attack surface'
    56. 

  56.          documentation for details: https://docs.docker.com/go/attack-surface/
    57. 

    58. 

  58. ================================================================================
    59.

（2）安装 Docker Engine-Community

  1. sudo yum install -y yum-utils device-mapper-persistent-data lvm2

执行后效果

    

  1. [root@localhost base]# sudo yum install -y yum-utils \
    2. 

  2. > device-mapper-persistent-data \
    3. 

  3. > lvm2
    4. 

  4. Loaded plugins: fastestmirror, langpacks
    5. 

  5. Loading mirror speeds from cached hostfile
    6. 

  6.  * base: mirrors.aliyun.com
    7. 

  7.  * extras: mirrors.aliyun.com
    8. 

  8.  * updates: mirrors.aliyun.com
    9. 

  9. Package yum-utils-1.1.31-54.el7_8.noarch already installed and latest version
    10. 

  10. Resolving Dependencies
    11. 

  11. --> Running transaction check
    12. 

  12. ---> Package device-mapper-persistent-data.x86_64 0:0.6.3-1.el7 will be updated
    13. 

  13. ---> Package device-mapper-persistent-data.x86_64 0:0.8.5-3.el7_9.2 will be an update
    14. 

  14. ---> Package lvm2.x86_64 7:2.02.166-1.el7 will be updated
    15. 

  15. ---> Package lvm2.x86_64 7:2.02.187-6.el7_9.5 will be an update
    16. 

  16. --> Processing Dependency: lvm2-libs = 7:2.02.187-6.el7_9.5 for package: 7:lvm2-2.02.187-6.el7_9.5.x86_64
    17. 

  17. --> Processing Dependency: libdevmapper.so.1.02(DM_1_02_141)(64bit) for package: 7:lvm2-2.02.187-6.el7_9.5.x86_64
    18. 

  18. --> Processing Dependency: libdevmapper.so.1.02(DM_1_02_138)(64bit) for package: 7:lvm2-2.02.187-6.el7_9.5.x86_64
    19. 

  19. --> Running transaction check
    20. 

  20. ---> Package device-mapper-libs.x86_64 7:1.02.135-1.el7 will be updated
    21. 

  21. --> Processing Dependency: device-mapper-libs = 7:1.02.135-1.el7 for package: 7:device-mapper-1.02.135-1.el7.x86_64
    22. 

  22. ---> Package device-mapper-libs.x86_64 7:1.02.170-6.el7_9.5 will be an update
    23. 

  23. ---> Package lvm2-libs.x86_64 7:2.02.166-1.el7 will be updated
    24. 

  24. ---> Package lvm2-libs.x86_64 7:2.02.187-6.el7_9.5 will be an update
    25. 

  25. --> Processing Dependency: device-mapper-event = 7:1.02.170-6.el7_9.5 for package: 7:lvm2-libs-2.02.187-6.el7_9.5.x86_64
    26. 

  26. --> Running transaction check
    27. 

  27. ---> Package device-mapper.x86_64 7:1.02.135-1.el7 will be updated
    28. 

  28. ---> Package device-mapper.x86_64 7:1.02.170-6.el7_9.5 will be an update
    29. 

  29. ---> Package device-mapper-event.x86_64 7:1.02.135-1.el7 will be updated
    30. 

  30. ---> Package device-mapper-event.x86_64 7:1.02.170-6.el7_9.5 will be an update
    31. 

  31. --> Processing Dependency: device-mapper-event-libs = 7:1.02.170-6.el7_9.5 for package: 7:device-mapper-event-1.02.170-6.el7_9.5.x86_64
    32. 

  32. --> Running transaction check
    33. 

  33. ---> Package device-mapper-event-libs.x86_64 7:1.02.135-1.el7 will be updated
    34. 

  34. ---> Package device-mapper-event-libs.x86_64 7:1.02.170-6.el7_9.5 will be an update
    35. 

  35. --> Finished Dependency Resolution
    36. 

    37. 

  37. Dependencies Resolved
    38. 

    39. 

  39. ============================================================================================================================================================================================
    40. 

  40.  Package                                                   Arch                               Version                                             Repository                           Size
    41. 

  41. ============================================================================================================================================================================================
    42. 

  42. Updating:
    43. 

  43.  device-mapper-persistent-data                             x86_64                             0.8.5-3.el7_9.2                                     updates                             423 k
    44. 

  44.  lvm2                                                      x86_64                             7:2.02.187-6.el7_9.5                                updates                             1.3 M
    45. 

  45. Updating for dependencies:
    46. 

  46.  device-mapper                                             x86_64                             7:1.02.170-6.el7_9.5                                updates                             297 k
    47. 

  47.  device-mapper-event                                       x86_64                             7:1.02.170-6.el7_9.5                                updates                             192 k
    48. 

  48.  device-mapper-event-libs                                  x86_64                             7:1.02.170-6.el7_9.5                                updates                             192 k
    49. 

  49.  device-mapper-libs                                        x86_64                             7:1.02.170-6.el7_9.5                                updates                             325 k
    50. 

  50.  lvm2-libs                                                 x86_64                             7:2.02.187-6.el7_9.5                                updates                             1.1 M
    51. 

    52. 

  52. Transaction Summary
    53. 

  53. ============================================================================================================================================================================================
    54. 

  54. Upgrade  2 Packages (+5 Dependent packages)
    55. 

    56. 

  56. Total size: 3.8 M
    57. 

  57. Downloading packages:
    58. 

  58. Running transaction check
    59. 

  59. Running transaction test
    60. 

  60. Transaction test succeeded
    61. 

  61. Running transaction
    62. 

  62.   Updating   : 7:device-mapper-libs-1.02.170-6.el7_9.5.x86_64                                                                                                                          1/14
    63. 

  63.   Updating   : 7:device-mapper-1.02.170-6.el7_9.5.x86_64                                                                                                                               2/14
    64. 

  64.   Updating   : 7:device-mapper-event-libs-1.02.170-6.el7_9.5.x86_64                                                                                                                    3/14
    65. 

  65.   Updating   : 7:device-mapper-event-1.02.170-6.el7_9.5.x86_64                                                                                                                         4/14
    66. 

  66.   Updating   : 7:lvm2-libs-2.02.187-6.el7_9.5.x86_64                                                                                                                                   5/14
    67. 

  67.   Updating   : device-mapper-persistent-data-0.8.5-3.el7_9.2.x86_64                                                                                                                    6/14
    68. 

  68.   Updating   : 7:lvm2-2.02.187-6.el7_9.5.x86_64                                                                                                                                        7/14
    69. 

  69.   Cleanup    : 7:lvm2-2.02.166-1.el7.x86_64                                                                                                                                            8/14
    70. 

  70.   Cleanup    : 7:lvm2-libs-2.02.166-1.el7.x86_64                                                                                                                                       9/14
    71. 

  71.   Cleanup    : 7:device-mapper-event-1.02.135-1.el7.x86_64                                                                                                                            10/14
    72. 

  72.   Cleanup    : 7:device-mapper-event-libs-1.02.135-1.el7.x86_64                                                                                                                       11/14
    73. 

  73.   Cleanup    : 7:device-mapper-1.02.135-1.el7.x86_64                                                                                                                                  12/14
    74. 

  74.   Cleanup    : 7:device-mapper-libs-1.02.135-1.el7.x86_64                                                                                                                             13/14
    75. 

  75.   Cleanup    : device-mapper-persistent-data-0.6.3-1.el7.x86_64                                                                                                                       14/14
    76. 

  76.   Verifying  : 7:device-mapper-event-1.02.170-6.el7_9.5.x86_64                                                                                                                         1/14
    77. 

  77.   Verifying  : 7:lvm2-libs-2.02.187-6.el7_9.5.x86_64                                                                                                                                   2/14
    78. 

  78.   Verifying  : device-mapper-persistent-data-0.8.5-3.el7_9.2.x86_64                                                                                                                    3/14
    79. 

  79.   Verifying  : 7:device-mapper-1.02.170-6.el7_9.5.x86_64                                                                                                                               4/14
    80. 

  80.   Verifying  : 7:device-mapper-event-libs-1.02.170-6.el7_9.5.x86_64                                                                                                                    5/14
    81. 

  81.   Verifying  : 7:lvm2-2.02.187-6.el7_9.5.x86_64                                                                                                                                        6/14
    82. 

  82.   Verifying  : 7:device-mapper-libs-1.02.170-6.el7_9.5.x86_64                                                                                                                          7/14
    83. 

  83.   Verifying  : 7:device-mapper-event-libs-1.02.135-1.el7.x86_64                                                                                                                        8/14
    84. 

  84.   Verifying  : 7:device-mapper-libs-1.02.135-1.el7.x86_64                                                                                                                              9/14
    85. 

  85.   Verifying  : 7:lvm2-2.02.166-1.el7.x86_64                                                                                                                                           10/14
    86. 

  86.   Verifying  : device-mapper-persistent-data-0.6.3-1.el7.x86_64                                                                                                                       11/14
    87. 

  87.   Verifying  : 7:device-mapper-1.02.135-1.el7.x86_64                                                                                                                                  12/14
    88. 

  88.   Verifying  : 7:lvm2-libs-2.02.166-1.el7.x86_64                                                                                                                                      13/14
    89. 

  89.   Verifying  : 7:device-mapper-event-1.02.135-1.el7.x86_64                                                                                                                            14/14
    90. 

    91. 

  91. Updated:
    92. 

  92.   device-mapper-persistent-data.x86_64 0:0.8.5-3.el7_9.2                                                  lvm2.x86_64 7:2.02.187-6.el7_9.5
    93. 

    94. 

  94. Dependency Updated:
    95. 

  95.   device-mapper.x86_64 7:1.02.170-6.el7_9.5                   device-mapper-event.x86_64 7:1.02.170-6.el7_9.5              device-mapper-event-libs.x86_64 7:1.02.170-6.el7_9.5
    96. 

  96.   device-mapper-libs.x86_64 7:1.02.170-6.el7_9.5              lvm2-libs.x86_64 7:2.02.187-6.el7_9.5
    97. 

    98. 

  98. Complete!
    99.

（3）启动并检查docker状态

    

  1. sudo systemctl start docker
    2. 

  2. sudo systemctl status docker
    3. 

    

  1. [root@localhost base]# sudo systemctl start docker
    2. 

  2. [root@localhost base]# sudo systemctl status docker
    3. 

  3. ● docker.service - Docker Application Container Engine
    4. 

  4.    Loaded: loaded (/etc/systemd/system/docker.service; disabled; vendor preset: disabled)
    5. 

  5.    Active: active (running) since Wed 2022-01-05 16:59:36 CST; 19min ago
    6. 

  6.      Docs: https://docs.docker.com
    7. 

  7.  Main PID: 97399 (dockerd)
    8. 

  8.     Tasks: 0
    9. 

  9.    Memory: 58.8M
    10. 

  10.    CGroup: /system.slice/docker.service
    11. 

  11.            ├─97399 /usr/bin/dockerd
    12. 

  12.            └─97412 containerd --config /var/run/docker/containerd/containerd.toml --log-level info
    13. 

    14. 

  14. Jan 05 17:00:23 localhost.localdomain dockerd[97399]: time="2022-01-05T17:00:23.218537488+08:00" level=info msg="Attempting next endpoint for pull after error: Head \"https:/...ke timeout"
    15. 

  15. Jan 05 17:00:23 localhost.localdomain dockerd[97399]: time="2022-01-05T17:00:23.221555539+08:00" level=error msg="Handler for POST /v1.41/images/create returned error: Head \...ke timeout"
    16. 

  16. Jan 05 17:01:10 localhost.localdomain dockerd[97399]: time="2022-01-05T17:01:10.059479965+08:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/contain...d pid=98227
    17. 

  17. Jan 05 17:01:10 localhost.localdomain dockerd[97399]: time="2022-01-05T17:01:10.357324081+08:00" level=info msg="ignoring event" container=8149b29cadca1403bfe1df665f4a608bb01...TaskDelete"
    18. 

  18. Jan 05 17:01:10 localhost.localdomain dockerd[97399]: time="2022-01-05T17:01:10.359788730+08:00" level=info msg="shim disconnected" id=8149b29cadca1403bfe1df665f4a608bb0197e7...3141c638efd
    19. 

  19. Jan 05 17:01:10 localhost.localdomain dockerd[97399]: time="2022-01-05T17:01:10.359881885+08:00" level=error msg="copy shim log" error="read /proc/self/fd/14: file already closed"
    20. 

  20. Jan 05 17:01:17 localhost.localdomain dockerd[97399]: time="2022-01-05T17:01:17.341227632+08:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/contain...1 pid=98362
    21. 

  21. Jan 05 17:01:17 localhost.localdomain dockerd[97399]: time="2022-01-05T17:01:17.593448271+08:00" level=info msg="ignoring event" container=9a183ecff69e89963aa86351f53bb9d51d5...TaskDelete"
    22. 

  22. Jan 05 17:01:17 localhost.localdomain dockerd[97399]: time="2022-01-05T17:01:17.594207060+08:00" level=info msg="shim disconnected" id=9a183ecff69e89963aa86351f53bb9d51d5ca53...1fd409b3e11
    23. 

  23. Jan 05 17:01:17 localhost.localdomain dockerd[97399]: time="2022-01-05T17:01:17.594300540+08:00" level=error msg="copy shim log" error="read /proc/self/fd/14: file already closed"
    24. 

  24. Hint: Some lines were ellipsized, use -l to show in full.
    25.

二、安装metersphere

(1)离线安装metersphere

  1. tail -zxvf metersphere-offline-installer-v1.15.4.tar.gz
  1. cd metersphere-offline-installer-v1.15.4/
  1. sudo sh install.sh
    

  1. [root@localhost base]# tail -zxvf metersphere-offline-installer-v1.15.4.tar.gz
    2. 

  2. [root@localhost base]# cd metersphere-offline-installer-v1.15.4/
    3. 

  3. [root@localhost metersphere-offline-installer-v1.15.4]# sudo sh install.sh
    4. 

  4. 存在已安装的 MeterSphere, 安装目录为 /opt/metersphere, 执行升级流程
    5. 

  5. [MeterSphere Log]: 拷贝安装文件到目标目录
    6. 

  6. ‘./metersphere/docker-compose-kafka.yml’ -> ‘/opt/metersphere/docker-compose-kafka.yml’ (backup: ‘/opt/metersphere/docker-compose-kafka.yml.20220105-1719’)
    7. 

  7. ‘./metersphere/docker-compose-prometheus.yml’ -> ‘/opt/metersphere/docker-compose-prometheus.yml’ (backup: ‘/opt/metersphere/docker-compose-prometheus.yml.20220105-1719’)
    8. 

  8. ‘./metersphere/docker-compose-node-controller.yml’ -> ‘/opt/metersphere/docker-compose-node-controller.yml’ (backup: ‘/opt/metersphere/docker-compose-node-controller.yml.20220105-1719’)
    9. 

  9. ‘./metersphere/docker-compose-mysql.yml’ -> ‘/opt/metersphere/docker-compose-mysql.yml’ (backup: ‘/opt/metersphere/docker-compose-mysql.yml.20220105-1719’)
    10. 

  10. ‘./metersphere/conf/my.cnf’ -> ‘/opt/metersphere/conf/my.cnf’ (backup: ‘/opt/metersphere/conf/my.cnf.20220105-1719’)
    11. 

  11. ‘./metersphere/conf/version’ -> ‘/opt/metersphere/conf/version’ (backup: ‘/opt/metersphere/conf/version.20220105-1719’)
    12. 

  12. ‘./metersphere/conf/prometheus/prometheus.yml’ -> ‘/opt/metersphere/conf/prometheus/prometheus.yml’ (backup: ‘/opt/metersphere/conf/prometheus/prometheus.yml.20220105-1719’)
    13. 

  13. ‘./metersphere/conf/metersphere.properties’ -> ‘/opt/metersphere/conf/metersphere.properties’ (backup: ‘/opt/metersphere/conf/metersphere.properties.20220105-1719’)
    14. 

  14. ‘./metersphere/version’ -> ‘/opt/metersphere/version’ (backup: ‘/opt/metersphere/version.20220105-1719’)
    15. 

  15. ‘./metersphere/docker-compose-base.yml’ -> ‘/opt/metersphere/docker-compose-base.yml’ (backup: ‘/opt/metersphere/docker-compose-base.yml.20220105-1719’)
    16. 

  16. ‘./metersphere/docker-compose-server.yml’ -> ‘/opt/metersphere/docker-compose-server.yml’ (backup: ‘/opt/metersphere/docker-compose-server.yml.20220105-1719’)
    17. 

  17. ‘./metersphere/logs/README.md’ -> ‘/opt/metersphere/logs/README.md’ (backup: ‘/opt/metersphere/logs/README.md.20220105-1719’)
    18. 

  18. [MeterSphere Log]: ======================= 开始安装 =======================
    19. 

  19. [MeterSphere Log]: 检测到 Docker 已安装，跳过安装步骤
    20. 

  20. [MeterSphere Log]: 启动 Docker
    21. 

  21. Redirecting to /bin/systemctl start docker.service
    22. 

  22. [MeterSphere Log]: 检测到 Docker Compose 已安装，跳过安装步骤
    23. 

  23. [MeterSphere Log]: 加载镜像
    24. 

  24. Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/jmeter-master:5.4.1-ms13-jdk8
    25. 

  25. Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/kafka:2
    26. 

  26. Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/metersphere:v1.15.4
    27. 

  27. Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/ms-data-streaming:v1.15.4
    28. 

  28. Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/ms-node-controller:v1.15.4
    29. 

  29. Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/mysql:5.7.33
    30. 

  30. Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/node-exporter:latest
    31. 

  31. Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/prometheus:latest
    32. 

  32. Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/zookeeper:3
    33. 

  33. [MeterSphere Log]: 启动服务
    34. 

    35. 

  35. Removing network metersphere_ms-network
    36. 

  36. Network metersphere_ms-network not found.
    37. 

  37. Removing volume metersphere_ms-conf
    38. 

  38. Volume metersphere_ms-conf not found.
    39. 

  39. Removing volume metersphere_ms-logs
    40. 

  40. Volume metersphere_ms-logs not found.
    41. 

  41. Removing volume metersphere_ms-data
    42. 

  42. Volume metersphere_ms-data not found.
    43. 

  43. Removing volume metersphere_ms-mysql-data
    44. 

  44. Volume metersphere_ms-mysql-data not found.
    45. 

  45. Removing volume metersphere_ms-zookeeper-data
    46. 

  46. Volume metersphere_ms-zookeeper-data not found.
    47. 

  47. Removing volume metersphere_ms-kafka-data
    48. 

  48. Volume metersphere_ms-kafka-data not found.
    49. 

  49. Removing volume metersphere_ms-prometheus-data
    50. 

  50. Volume metersphere_ms-prometheus-data not found.
    51. 

  51. Removing volume metersphere_ms-prometheus-conf
    52. 

  52. Volume metersphere_ms-prometheus-conf not found.
    53. 

    54. 

  54. Creating network "metersphere_ms-network" with driver "bridge"
    55. 

  55. Creating volume "metersphere_ms-conf" with default driver
    56. 

  56. Creating volume "metersphere_ms-logs" with default driver
    57. 

  57. Creating volume "metersphere_ms-data" with default driver
    58. 

  58. Creating volume "metersphere_ms-mysql-data" with default driver
    59. 

  59. Creating volume "metersphere_ms-zookeeper-data" with default driver
    60. 

  60. Creating volume "metersphere_ms-kafka-data" with default driver
    61. 

  61. Creating volume "metersphere_ms-prometheus-data" with default driver
    62. 

  62. Creating volume "metersphere_ms-prometheus-conf" with default driver
    63. 

  63. Creating zookeeper          ... done
    64. 

  64. Creating mysql              ... done
    65. 

  65. Creating ms-prometheus      ... done
    66. 

  66. Creating ms-node-controller ... done
    67. 

  67. Creating kafka              ... done
    68. 

  68. Creating nodeexporter       ... done
    69. 

  69. Creating ms-server          ... done
    70. 

  70. Creating ms-data-streaming  ... done
    71. 

    72. 

  72.        Name                     Command                       State                                                               Ports
    73. 

  73. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    74. 

  74. kafka                /opt/bitnami/scripts/kafka ...   Up (healthy)            0.0.0.0:19092->19092/tcp,:::19092->19092/tcp, 9092/tcp
    75. 

  75. ms-data-streaming    /deployments/run-java.sh         Up (health: starting)
    76. 

  76. ms-node-controller   /deployments/run-java.sh         Up (health: starting)   0.0.0.0:8082->8082/tcp,:::8082->8082/tcp, 0.0.0.0:9100->9100/tcp,:::9100->9100/tcp
    77. 

  77. ms-prometheus        /bin/prometheus --config.f ...   Up (healthy)            0.0.0.0:9090->9090/tcp,:::9090->9090/tcp
    78. 

  78. ms-server            /deployments/run-java.sh         Up (health: starting)   0.0.0.0:10000->10000/tcp,:::10000->10000/tcp, 0.0.0.0:10001->10001/tcp,:::10001->10001/tcp,
    79. 

  79.                                                                               0.0.0.0:10002->10002/tcp,:::10002->10002/tcp, 0.0.0.0:10003->10003/tcp,:::10003->10003/tcp,
    80. 

  80.                                                                               0.0.0.0:10004->10004/tcp,:::10004->10004/tcp, 0.0.0.0:10005->10005/tcp,:::10005->10005/tcp,
    81. 

  81.                                                                               0.0.0.0:10006->10006/tcp,:::10006->10006/tcp, 0.0.0.0:10007->10007/tcp,:::10007->10007/tcp,
    82. 

  82.                                                                               0.0.0.0:10008->10008/tcp,:::10008->10008/tcp, 0.0.0.0:10009->10009/tcp,:::10009->10009/tcp,
    83. 

  83.                                                                               0.0.0.0:10010->10010/tcp,:::10010->10010/tcp, 0.0.0.0:8081->8081/tcp,:::8081->8081/tcp
    84. 

  84. mysql                docker-entrypoint.sh mysqld      Up (healthy)            0.0.0.0:3307->3306/tcp,:::3307->3306/tcp, 33060/tcp
    85. 

  85. nodeexporter         /bin/node_exporter --path. ...   Up (healthy)
    86. 

  86. zookeeper            /opt/bitnami/scripts/zooke ...   Up (healthy)            2181/tcp, 2888/tcp, 3888/tcp, 8080/tcp
    87. 

  87. ======================= 安装完成 =======================
    88. 

    89. 

  89. 请通过以下方式访问:
    90. 

  90.  URL: http://$LOCAL_IP:8081
    91. 

  91.  用户名: admin
    92. 

  92.  初始密码: metersphere
    93. 

  93. 您可以使用命令 'msctl status' 检查服务运行情况.
    94.

（2）检查服务运行情况

  1. sudo msctl status
    

  1. [root@localhost metersphere-offline-installer-v1.15.4]# sudo msctl status
    2. 

    3. 

  3.        Name                     Command                       State                                                               Ports
    4. 

  4. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    5. 

  5. kafka                /opt/bitnami/scripts/kafka ...   Up (healthy)            0.0.0.0:19092->19092/tcp,:::19092->19092/tcp, 9092/tcp
    6. 

  6. ms-data-streaming    /deployments/run-java.sh         Up (healthy)
    7. 

  7. ms-node-controller   /deployments/run-java.sh         Up (healthy)            0.0.0.0:8082->8082/tcp,:::8082->8082/tcp, 0.0.0.0:9100->9100/tcp,:::9100->9100/tcp
    8. 

  8. ms-prometheus        /bin/prometheus --config.f ...   Up (healthy)            0.0.0.0:9090->9090/tcp,:::9090->9090/tcp
    9. 

  9. ms-server            /deployments/run-java.sh         Up (health: starting)   0.0.0.0:10000->10000/tcp,:::10000->10000/tcp, 0.0.0.0:10001->10001/tcp,:::10001->10001/tcp,
    10. 

  10.                                                                               0.0.0.0:10002->10002/tcp,:::10002->10002/tcp, 0.0.0.0:10003->10003/tcp,:::10003->10003/tcp,
    11. 

  11.                                                                               0.0.0.0:10004->10004/tcp,:::10004->10004/tcp, 0.0.0.0:10005->10005/tcp,:::10005->10005/tcp,
    12. 

  12.                                                                               0.0.0.0:10006->10006/tcp,:::10006->10006/tcp, 0.0.0.0:10007->10007/tcp,:::10007->10007/tcp,
    13. 

  13.                                                                               0.0.0.0:10008->10008/tcp,:::10008->10008/tcp, 0.0.0.0:10009->10009/tcp,:::10009->10009/tcp,
    14. 

  14.                                                                               0.0.0.0:10010->10010/tcp,:::10010->10010/tcp, 0.0.0.0:8081->8081/tcp,:::8081->8081/tcp
    15. 

  15. mysql                docker-entrypoint.sh mysqld      Up (healthy)            0.0.0.0:3307->3306/tcp,:::3307->3306/tcp, 33060/tcp
    16. 

  16. nodeexporter         /bin/node_exporter --path. ...   Up (healthy)
    17. 

  17. zookeeper            /opt/bitnami/scripts/zooke ...   Up (healthy)            2181/tcp, 2888/tcp, 3888/tcp, 8080/tcp
    18. 

  18. [root@localhost metersphere-offline-installer-v1.15.4]# netstat -antlpe | grep 8081
    19. 

  19. tcp        0      0 0.0.0.0:8081            0.0.0.0:*               LISTEN      0          282143     28166/docker-proxy
    20. 

  20. tcp6       0      0 :::8081                 :::*                    LISTEN      0          282150     28171/docker-proxy
    21.

三、访问刚刚搭建的meterSphere

请通过以下方式访问:
URL: http://$LOCAL_IP:8081
（我这里用的是Linux的主机IP登录：http://192.168.182.128:8081/login）
使用ifconfig即可查到IP信息，[如果这里没显示IP，可以先执行：sudo dhclient ens33，再执行ifconfig]

  1. ifconfig
    

  1. [bonree@localhost ~]$ ifconfig
    2. 

  2.  ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    3. 

  3.         inet 192.168.182.128  netmask 255.255.255.0  broadcast 192.168.182.255
    4. 

  4.         inet6 fe80::bccc:a8a0:6dd9:6969  prefixlen 64  scopeid 0x20<link>
    5. 

  5.         ether 00:0c:29:ea:bc:d4  txqueuelen 1000  (Ethernet)
    6. 

  6.         RX packets 2473629  bytes 3524726711 (3.2 GiB)
    7. 

  7.         RX errors 0  dropped 0  overruns 0  frame 0
    8. 

  8.         TX packets 352058  bytes 45140138 (43.0 MiB)
    9. 

  9.         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    10.

用户名: admin
初始密码: metersphere
Linux上搭建meterSphere

本文转自：https://blog.csdn.net/weixin_45072910/article/details/122329016

上一篇： 树的深度优先与广度优先遍历

下一篇： 多吃豆类补气血 拒当黄脸婆 快点收藏吧

推荐阅读