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

一、安装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. # Executing docker install script, commit: 93d2499759296ac1f9c510605fef85052a2c32be
  3. Warning: the "docker" command appears to already exist on this system.
  4. If you already have Docker installed, this script can cause trouble, which is
  5. why we're displaying this warning and provide the opportunity to cancel the
  6. installation.
  7. If you installed the current Docker package using this script and are using it
  8. again to update Docker, you can safely ignore this message.
  9. You may press Ctrl+C now to abort this script.
  10. + sleep 20
  11. + sh -c 'yum install -y -q yum-utils'
  12. Package yum-utils-1.1.31-54.el7_8.noarch already installed and latest version
  13. + sh -c 'yum-config-manager --add-repo https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo'
  14. Loaded plugins: fastestmirror, langpacks
  15. adding repo from: https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
  16. grabbing file https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo to /etc/yum.repos.d/docker-ce.repo
  17. repo saved to /etc/yum.repos.d/docker-ce.repo
  18. + '[' stable '!=' stable ']'
  19. + sh -c 'yum makecache'
  20. Loaded plugins: fastestmirror, langpacks
  21. base | 3.6 kB 00:00:00
  22. docker-ce-stable | 3.5 kB 00:00:00
  23. extras | 2.9 kB 00:00:00
  24. updates | 2.9 kB 00:00:00
  25. Loading mirror speeds from cached hostfile
  26. * base: mirrors.aliyun.com
  27. * extras: mirrors.aliyun.com
  28. * updates: mirrors.aliyun.com
  29. Metadata Cache Created
  30. + '[' -n '' ']'
  31. + sh -c 'yum install -y -q docker-ce'
  32. + version_gte 20.10
  33. + '[' -z '' ']'
  34. + return 0
  35. + sh -c 'yum install -y -q docker-ce-rootless-extras'
  36. Package docker-ce-rootless-extras-20.10.12-3.el7.x86_64 already installed and latest version
  37. ================================================================================
  38. To run Docker as a non-privileged user, consider setting up the
  39. Docker daemon in rootless mode for your user:
  40. dockerd-rootless-setuptool.sh install
  41. Visit https://docs.docker.com/go/rootless/ to learn about rootless mode.
  42. To run the Docker daemon as a fully privileged service, but granting non-root
  43. users access, refer to https://docs.docker.com/go/daemon-access/
  44. WARNING: Access to the remote API on a privileged Docker daemon is equivalent
  45. to root access on the host. Refer to the 'Docker daemon attack surface'
  46. documentation for details: https://docs.docker.com/go/attack-surface/
  47. ================================================================================

(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. > device-mapper-persistent-data \
  3. > lvm2
  4. Loaded plugins: fastestmirror, langpacks
  5. Loading mirror speeds from cached hostfile
  6. * base: mirrors.aliyun.com
  7. * extras: mirrors.aliyun.com
  8. * updates: mirrors.aliyun.com
  9. Package yum-utils-1.1.31-54.el7_8.noarch already installed and latest version
  10. Resolving Dependencies
  11. --> Running transaction check
  12. ---> Package device-mapper-persistent-data.x86_64 0:0.6.3-1.el7 will be updated
  13. ---> Package device-mapper-persistent-data.x86_64 0:0.8.5-3.el7_9.2 will be an update
  14. ---> Package lvm2.x86_64 7:2.02.166-1.el7 will be updated
  15. ---> Package lvm2.x86_64 7:2.02.187-6.el7_9.5 will be an update
  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. --> 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. --> 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. --> Running transaction check
  20. ---> Package device-mapper-libs.x86_64 7:1.02.135-1.el7 will be updated
  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. ---> Package device-mapper-libs.x86_64 7:1.02.170-6.el7_9.5 will be an update
  23. ---> Package lvm2-libs.x86_64 7:2.02.166-1.el7 will be updated
  24. ---> Package lvm2-libs.x86_64 7:2.02.187-6.el7_9.5 will be an update
  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. --> Running transaction check
  27. ---> Package device-mapper.x86_64 7:1.02.135-1.el7 will be updated
  28. ---> Package device-mapper.x86_64 7:1.02.170-6.el7_9.5 will be an update
  29. ---> Package device-mapper-event.x86_64 7:1.02.135-1.el7 will be updated
  30. ---> Package device-mapper-event.x86_64 7:1.02.170-6.el7_9.5 will be an update
  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. --> Running transaction check
  33. ---> Package device-mapper-event-libs.x86_64 7:1.02.135-1.el7 will be updated
  34. ---> Package device-mapper-event-libs.x86_64 7:1.02.170-6.el7_9.5 will be an update
  35. --> Finished Dependency Resolution
  36. Dependencies Resolved
  37. ============================================================================================================================================================================================
  38. Package Arch Version Repository Size
  39. ============================================================================================================================================================================================
  40. Updating:
  41. device-mapper-persistent-data x86_64 0.8.5-3.el7_9.2 updates 423 k
  42. lvm2 x86_64 7:2.02.187-6.el7_9.5 updates 1.3 M
  43. Updating for dependencies:
  44. device-mapper x86_64 7:1.02.170-6.el7_9.5 updates 297 k
  45. device-mapper-event x86_64 7:1.02.170-6.el7_9.5 updates 192 k
  46. device-mapper-event-libs x86_64 7:1.02.170-6.el7_9.5 updates 192 k
  47. device-mapper-libs x86_64 7:1.02.170-6.el7_9.5 updates 325 k
  48. lvm2-libs x86_64 7:2.02.187-6.el7_9.5 updates 1.1 M
  49. Transaction Summary
  50. ============================================================================================================================================================================================
  51. Upgrade 2 Packages (+5 Dependent packages)
  52. Total size: 3.8 M
  53. Downloading packages:
  54. Running transaction check
  55. Running transaction test
  56. Transaction test succeeded
  57. Running transaction
  58. Updating : 7:device-mapper-libs-1.02.170-6.el7_9.5.x86_64 1/14
  59. Updating : 7:device-mapper-1.02.170-6.el7_9.5.x86_64 2/14
  60. Updating : 7:device-mapper-event-libs-1.02.170-6.el7_9.5.x86_64 3/14
  61. Updating : 7:device-mapper-event-1.02.170-6.el7_9.5.x86_64 4/14
  62. Updating : 7:lvm2-libs-2.02.187-6.el7_9.5.x86_64 5/14
  63. Updating : device-mapper-persistent-data-0.8.5-3.el7_9.2.x86_64 6/14
  64. Updating : 7:lvm2-2.02.187-6.el7_9.5.x86_64 7/14
  65. Cleanup : 7:lvm2-2.02.166-1.el7.x86_64 8/14
  66. Cleanup : 7:lvm2-libs-2.02.166-1.el7.x86_64 9/14
  67. Cleanup : 7:device-mapper-event-1.02.135-1.el7.x86_64 10/14
  68. Cleanup : 7:device-mapper-event-libs-1.02.135-1.el7.x86_64 11/14
  69. Cleanup : 7:device-mapper-1.02.135-1.el7.x86_64 12/14
  70. Cleanup : 7:device-mapper-libs-1.02.135-1.el7.x86_64 13/14
  71. Cleanup : device-mapper-persistent-data-0.6.3-1.el7.x86_64 14/14
  72. Verifying : 7:device-mapper-event-1.02.170-6.el7_9.5.x86_64 1/14
  73. Verifying : 7:lvm2-libs-2.02.187-6.el7_9.5.x86_64 2/14
  74. Verifying : device-mapper-persistent-data-0.8.5-3.el7_9.2.x86_64 3/14
  75. Verifying : 7:device-mapper-1.02.170-6.el7_9.5.x86_64 4/14
  76. Verifying : 7:device-mapper-event-libs-1.02.170-6.el7_9.5.x86_64 5/14
  77. Verifying : 7:lvm2-2.02.187-6.el7_9.5.x86_64 6/14
  78. Verifying : 7:device-mapper-libs-1.02.170-6.el7_9.5.x86_64 7/14
  79. Verifying : 7:device-mapper-event-libs-1.02.135-1.el7.x86_64 8/14
  80. Verifying : 7:device-mapper-libs-1.02.135-1.el7.x86_64 9/14
  81. Verifying : 7:lvm2-2.02.166-1.el7.x86_64 10/14
  82. Verifying : device-mapper-persistent-data-0.6.3-1.el7.x86_64 11/14
  83. Verifying : 7:device-mapper-1.02.135-1.el7.x86_64 12/14
  84. Verifying : 7:lvm2-libs-2.02.166-1.el7.x86_64 13/14
  85. Verifying : 7:device-mapper-event-1.02.135-1.el7.x86_64 14/14
  86. Updated:
  87. 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
  88. Dependency Updated:
  89. 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
  90. 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
  91. Complete!

(3)启动并检查docker状态

  1. sudo systemctl start docker
  2. sudo systemctl status docker
  1. [root@localhost base]# sudo systemctl start docker
  2. [root@localhost base]# sudo systemctl status docker
  3. docker.service - Docker Application Container Engine
  4. Loaded: loaded (/etc/systemd/system/docker.service; disabled; vendor preset: disabled)
  5. Active: active (running) since Wed 2022-01-05 16:59:36 CST; 19min ago
  6. Docs: https://docs.docker.com
  7. Main PID: 97399 (dockerd)
  8. Tasks: 0
  9. Memory: 58.8M
  10. CGroup: /system.slice/docker.service
  11. ├─97399 /usr/bin/dockerd
  12. └─97412 containerd --config /var/run/docker/containerd/containerd.toml --log-level info
  13. 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"
  14. 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"
  15. 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
  16. 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"
  17. 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
  18. 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"
  19. 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
  20. 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"
  21. 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
  22. 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"
  23. Hint: Some lines were ellipsized, use -l to show in full.

二、安装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. [root@localhost base]# cd metersphere-offline-installer-v1.15.4/
  3. [root@localhost metersphere-offline-installer-v1.15.4]# sudo sh install.sh
  4. 存在已安装的 MeterSphere, 安装目录为 /opt/metersphere, 执行升级流程
  5. [MeterSphere Log]: 拷贝安装文件到目标目录
  6. ‘./metersphere/docker-compose-kafka.yml -> ‘/opt/metersphere/docker-compose-kafka.yml (backup: ‘/opt/metersphere/docker-compose-kafka.yml.20220105-1719’)
  7. ‘./metersphere/docker-compose-prometheus.yml -> ‘/opt/metersphere/docker-compose-prometheus.yml (backup: ‘/opt/metersphere/docker-compose-prometheus.yml.20220105-1719’)
  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. ‘./metersphere/docker-compose-mysql.yml -> ‘/opt/metersphere/docker-compose-mysql.yml (backup: ‘/opt/metersphere/docker-compose-mysql.yml.20220105-1719’)
  10. ‘./metersphere/conf/my.cnf -> ‘/opt/metersphere/conf/my.cnf (backup: ‘/opt/metersphere/conf/my.cnf.20220105-1719’)
  11. ‘./metersphere/conf/version -> ‘/opt/metersphere/conf/version (backup: ‘/opt/metersphere/conf/version.20220105-1719’)
  12. ‘./metersphere/conf/prometheus/prometheus.yml -> ‘/opt/metersphere/conf/prometheus/prometheus.yml (backup: ‘/opt/metersphere/conf/prometheus/prometheus.yml.20220105-1719’)
  13. ‘./metersphere/conf/metersphere.properties -> ‘/opt/metersphere/conf/metersphere.properties (backup: ‘/opt/metersphere/conf/metersphere.properties.20220105-1719’)
  14. ‘./metersphere/version -> ‘/opt/metersphere/version (backup: ‘/opt/metersphere/version.20220105-1719’)
  15. ‘./metersphere/docker-compose-base.yml -> ‘/opt/metersphere/docker-compose-base.yml (backup: ‘/opt/metersphere/docker-compose-base.yml.20220105-1719’)
  16. ‘./metersphere/docker-compose-server.yml -> ‘/opt/metersphere/docker-compose-server.yml (backup: ‘/opt/metersphere/docker-compose-server.yml.20220105-1719’)
  17. ‘./metersphere/logs/README.md -> ‘/opt/metersphere/logs/README.md (backup: ‘/opt/metersphere/logs/README.md.20220105-1719’)
  18. [MeterSphere Log]: ======================= 开始安装 =======================
  19. [MeterSphere Log]: 检测到 Docker 已安装,跳过安装步骤
  20. [MeterSphere Log]: 启动 Docker
  21. Redirecting to /bin/systemctl start docker.service
  22. [MeterSphere Log]: 检测到 Docker Compose 已安装,跳过安装步骤
  23. [MeterSphere Log]: 加载镜像
  24. Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/jmeter-master:5.4.1-ms13-jdk8
  25. Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/kafka:2
  26. Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/metersphere:v1.15.4
  27. Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/ms-data-streaming:v1.15.4
  28. Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/ms-node-controller:v1.15.4
  29. Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/mysql:5.7.33
  30. Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/node-exporter:latest
  31. Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/prometheus:latest
  32. Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/zookeeper:3
  33. [MeterSphere Log]: 启动服务
  34. Removing network metersphere_ms-network
  35. Network metersphere_ms-network not found.
  36. Removing volume metersphere_ms-conf
  37. Volume metersphere_ms-conf not found.
  38. Removing volume metersphere_ms-logs
  39. Volume metersphere_ms-logs not found.
  40. Removing volume metersphere_ms-data
  41. Volume metersphere_ms-data not found.
  42. Removing volume metersphere_ms-mysql-data
  43. Volume metersphere_ms-mysql-data not found.
  44. Removing volume metersphere_ms-zookeeper-data
  45. Volume metersphere_ms-zookeeper-data not found.
  46. Removing volume metersphere_ms-kafka-data
  47. Volume metersphere_ms-kafka-data not found.
  48. Removing volume metersphere_ms-prometheus-data
  49. Volume metersphere_ms-prometheus-data not found.
  50. Removing volume metersphere_ms-prometheus-conf
  51. Volume metersphere_ms-prometheus-conf not found.
  52. Creating network "metersphere_ms-network" with driver "bridge"
  53. Creating volume "metersphere_ms-conf" with default driver
  54. Creating volume "metersphere_ms-logs" with default driver
  55. Creating volume "metersphere_ms-data" with default driver
  56. Creating volume "metersphere_ms-mysql-data" with default driver
  57. Creating volume "metersphere_ms-zookeeper-data" with default driver
  58. Creating volume "metersphere_ms-kafka-data" with default driver
  59. Creating volume "metersphere_ms-prometheus-data" with default driver
  60. Creating volume "metersphere_ms-prometheus-conf" with default driver
  61. Creating zookeeper ... done
  62. Creating mysql ... done
  63. Creating ms-prometheus ... done
  64. Creating ms-node-controller ... done
  65. Creating kafka ... done
  66. Creating nodeexporter ... done
  67. Creating ms-server ... done
  68. Creating ms-data-streaming ... done
  69. Name Command State Ports
  70. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  71. kafka /opt/bitnami/scripts/kafka ... Up (healthy) 0.0.0.0:19092->19092/tcp,:::19092->19092/tcp, 9092/tcp
  72. ms-data-streaming /deployments/run-java.sh Up (health: starting)
  73. 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
  74. ms-prometheus /bin/prometheus --config.f ... Up (healthy) 0.0.0.0:9090->9090/tcp,:::9090->9090/tcp
  75. 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,
  76. 0.0.0.0:10002->10002/tcp,:::10002->10002/tcp, 0.0.0.0:10003->10003/tcp,:::10003->10003/tcp,
  77. 0.0.0.0:10004->10004/tcp,:::10004->10004/tcp, 0.0.0.0:10005->10005/tcp,:::10005->10005/tcp,
  78. 0.0.0.0:10006->10006/tcp,:::10006->10006/tcp, 0.0.0.0:10007->10007/tcp,:::10007->10007/tcp,
  79. 0.0.0.0:10008->10008/tcp,:::10008->10008/tcp, 0.0.0.0:10009->10009/tcp,:::10009->10009/tcp,
  80. 0.0.0.0:10010->10010/tcp,:::10010->10010/tcp, 0.0.0.0:8081->8081/tcp,:::8081->8081/tcp
  81. mysql docker-entrypoint.sh mysqld Up (healthy) 0.0.0.0:3307->3306/tcp,:::3307->3306/tcp, 33060/tcp
  82. nodeexporter /bin/node_exporter --path. ... Up (healthy)
  83. zookeeper /opt/bitnami/scripts/zooke ... Up (healthy) 2181/tcp, 2888/tcp, 3888/tcp, 8080/tcp
  84. ======================= 安装完成 =======================
  85. 请通过以下方式访问:
  86. URL: http://$LOCAL_IP:8081
  87. 用户名: admin
  88. 初始密码: metersphere
  89. 您可以使用命令 'msctl status' 检查服务运行情况.

(2)检查服务运行情况

  1. sudo msctl status
  1. [root@localhost metersphere-offline-installer-v1.15.4]# sudo msctl status
  2. Name Command State Ports
  3. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  4. kafka /opt/bitnami/scripts/kafka ... Up (healthy) 0.0.0.0:19092->19092/tcp,:::19092->19092/tcp, 9092/tcp
  5. ms-data-streaming /deployments/run-java.sh Up (healthy)
  6. 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
  7. ms-prometheus /bin/prometheus --config.f ... Up (healthy) 0.0.0.0:9090->9090/tcp,:::9090->9090/tcp
  8. 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,
  9. 0.0.0.0:10002->10002/tcp,:::10002->10002/tcp, 0.0.0.0:10003->10003/tcp,:::10003->10003/tcp,
  10. 0.0.0.0:10004->10004/tcp,:::10004->10004/tcp, 0.0.0.0:10005->10005/tcp,:::10005->10005/tcp,
  11. 0.0.0.0:10006->10006/tcp,:::10006->10006/tcp, 0.0.0.0:10007->10007/tcp,:::10007->10007/tcp,
  12. 0.0.0.0:10008->10008/tcp,:::10008->10008/tcp, 0.0.0.0:10009->10009/tcp,:::10009->10009/tcp,
  13. 0.0.0.0:10010->10010/tcp,:::10010->10010/tcp, 0.0.0.0:8081->8081/tcp,:::8081->8081/tcp
  14. mysql docker-entrypoint.sh mysqld Up (healthy) 0.0.0.0:3307->3306/tcp,:::3307->3306/tcp, 33060/tcp
  15. nodeexporter /bin/node_exporter --path. ... Up (healthy)
  16. zookeeper /opt/bitnami/scripts/zooke ... Up (healthy) 2181/tcp, 2888/tcp, 3888/tcp, 8080/tcp
  17. [root@localhost metersphere-offline-installer-v1.15.4]# netstat -antlpe | grep 8081
  18. tcp 0 0 0.0.0.0:8081 0.0.0.0:* LISTEN 0 282143 28166/docker-proxy
  19. tcp6 0 0 :::8081 :::* LISTEN 0 282150 28171/docker-proxy

三、访问刚刚搭建的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. ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
  3. inet 192.168.182.128 netmask 255.255.255.0 broadcast 192.168.182.255
  4. inet6 fe80::bccc:a8a0:6dd9:6969 prefixlen 64 scopeid 0x20<link>
  5. ether 00:0c:29:ea:bc:d4 txqueuelen 1000 (Ethernet)
  6. RX packets 2473629 bytes 3524726711 (3.2 GiB)
  7. RX errors 0 dropped 0 overruns 0 frame 0
  8. TX packets 352058 bytes 45140138 (43.0 MiB)
  9. TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

用户名: admin
初始密码: metersphere

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

更多相关文章

  1. 在Ubuntu 9.10下编译Android源码
  2. Android源码下载并绑定到Eclipse中
  3. Android测试之ADB部署
  4. Android的Root原理
  5. Android——android studio 安装完成之后导入项目的乱码问题
  6. Android(安卓)NDK开发基础-------环境搭建1
  7. Android应用开发提高系列(5)――Android动态加载(下)――加载已安装A
  8. android 默认签名 debug签名
  9. Android生命周期中几个重要的函数

随机推荐

  1. Android(安卓)Jetpack-Navigation 初见
  2. android 常用 属性
  3. Android View的工作原理
  4. android 电容屏
  5. Android(安卓)缓存管理和LRU 算法
  6. Android Handler机制5之Message简介与消
  7. android 通过sheme打开activity
  8. Android 的Margin和Padding属性以及支持
  9. Android中RemoteViews的实现
  10. Android Switch属性全记录