Confirming Server Configuration of the FineReport Project

User Volume

Number of FineReport system users

You can estimate it based on the number of employees.

Number of users sending requests to the FineReport system per minute

You can estimate it following Number of system users * (0.5% to 5%).

Business Usage - Template Data Volume

Total number of template cells in all active sessions in the FineReport system

For multi-node clusters, this must be calculated based on the number of sessions across all nodes.

Business Usage - Data Entry

For customers with minimal business usage, FineReport and FineOps can be deployed on one server.

Main application server: 8-core CPU, 32 GB of memory, and 300 GB of disk space

It is used to deploy the FineReport application and Nginx (the internal gateway), MySQL (the configuration database), and Elasticsearch (the log storage service).

It is used to deploy all FineOps components.

Main application server: 16-core CPU, 64 GB of memory, and 500 GB of disk space

It is used to deploy the FineReport application and Nginx (the internal gateway), MySQL (the configuration database), and Elasticsearch (the log storage service).

It is used to deploy all FineOps components.

1. FineReport main application server: 16-core CPU, 64 GB of memory, and 300 GB of disk space

It is used to deploy the FineReport application.

2. Server for FineReport components and FineOps: 8-core CPU, 32 GB of memory, and 300 GB of disk space

It is used to deploy the following components: Nginx, MySQL, and Elasticsearch.

It is used to deploy all FineOps components.

1. FineReport main application server one: 16-core CPU, 64 GB of memory, and 200 GB of disk space

It is used to deploy the FineReport application.

2. FineReport main application server two: 16-core CPU, 64 GB of memory, and 200 GB of disk space

It is used to deploy the FineReport application.

3. Server for FineReport components and FineOps: 8-core CPU, 32 GB of memory, and 500 GB of disk space

It is used to deploy the following components: Nginx, MySQL, Elasticsearch, and the cluster component.

It is used to deploy all FineOps components.

1. N main application servers

N = (Number of System Users)/4000

Each main application server: 16-core CPU, 64 GB of memory, and 200 GB of disk space

Each main application server is used to deploy a FineReport application.

2. Server for FineReport components and FineOps: 8-core CPU, 32 GB of memory, and 500 GB of disk space

It is used to deploy the following components: Nginx, MySQL, Elasticsearch, and the cluster component.

It is used to deploy all FineOps components.

1. It is used to install the FineReport project as well as log and configuration components.

For details about the role of components, see Understanding the Roles of O&M Project Components.

• FineReport

• Nginx

• MySQL (The self-provided component is supported.)

• Elasticsearch (The self-provided component is supported.)

• Filebeat

• OPS Agent

2. It is used to install FineOps.

For details about the role of components, see Understanding the Roles of FineOps Components.

Note:

If you have installed FineOps, skip this part.

• OPS and Nginx

• Pushgateway, Prometheus, Grafana, and Alertmanager

• Elasticsearch and Skywalking OAP

• Registry (The self-provided component is supported.)

• OPS Agent

Recommended: Ubuntu 22

Supported:

• Ubuntu 18.04.4 and later releases (Ubuntu 20.04 is not supported.)

• CentOS 7.3 to 7.9

• Red Hat 7.6 and later releases

• Rocky Linux 8.8 to 9.4

Note:

You are advised to use Ubuntu since CentOS is discontinued.

When using Ubuntu, verify the user privilege (as the default root user is not a superuser). For details, see the notes in the following content.

The server shall have a partition with remaining free space of more than 300 GB.

Note:

There must be a single partition that meets the condition.

For details, see Preparing the FineReport Mounting Directory.

For details, see Preparing the FineOps Server.

Note:

The mounting path cannot be /, /usr, /root, or /usr/local. You can create folders in these paths for file mounting.

Ensure that the file system of the mounting directory is configured to be automatically mounted during a boot.

Otherwise, containers may fail to access these directories, leading to data loss or application startup issues.

The mounting path cannot be a shared-use path.

Sharing the file system may cause performance degradation, file permission issues, and data inconsistency, affecting the reliability and response speed of applications running in the container.

Ensure the server has tar installed.

tar is a commonly used command-line tool for archiving and compressing files.

FineOps requires this command to decompress files.

Ensure the server has sed installed.

The sed command is used for text processing.

FineOps requires this command to process text.

Ensure the user you use can connect to the FineOps server via the SSH protocol.

Ensure the password used for the SSH connection contains no English single quotation marks ('), or the privilege will fail to be validated during deployment.

The server user responsible for deploying the project must have the necessary sudo privileges.

1. You are advised to use the root user account for project deployment and operation.

2. To use a non-root user for deployment and operation, see Linux User Privilege Explanation.

Note:

The default root user of an Ubuntu operating system is not a superuser. Ensure the user privileges meet the requirements.

At least 20 Mbps (2.5 MB/s)

Note:

1. Increase the bandwidth accordingly as the number of concurrent project sessions grows.

2. If the business databases (databases connected via data connections) and self-provided components are all on the internal network, the required public internet bandwidth can be reduced accordingly.

Component-occupied port

Component port connectivity

For details, see Confirming the FineReport Server Network.

For details, see Preparing the FineOps Server.

If the server is running the Kylin operating system, ensure that Podman is not installed on the server.

The version of runc bundled with Podman is too low and conflicts with the Docker installation managed by FanRuan, which may cause deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

Ensure that Kingsoft Antivirus is not installed on the server.

This antivirus software may trigger server connection interruptions when the dockerd command is executed, resulting in deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

1. It is used to install the FineReport project as well as log and configuration components.

For details about the role of components, see Understanding the Roles of O&M Project Components.

• FineReport

• Nginx

• MySQL (The self-provided component is supported.)

• Elasticsearch (The self-provided component is supported.)

• Filebeat

• OPS Agent

2. It is used to install FineOps.

For details about the role of components, see Understanding the Roles of FineOps Components.

Note:

If you have installed FineOps, skip this part.

• OPS and Nginx

• Pushgateway, Prometheus, Grafana, and Alertmanager

• Elasticsearch and Skywalking OAP

• Registry (The self-provided component is supported.)

• OPS Agent

The time on all servers must be synchronized, with a maximum difference of no more than 5 seconds.

Inconsistent server time can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies.

All servers must be set to the same time zone.

Inconsistent server time zones can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies.

All servers can communicate with each other on the internal network or have open ports for access.

For details about port requirements, see the following content.

V3.10 and later versions

Recommended: Ubuntu 22

Supported:

• Ubuntu 18.04.4 and later releases (Ubuntu 20.04 is not supported.)

• CentOS 7.3 to 7.9

• Red Hat 7.6 and later releases

• Rocky Linux 8.8 to 9.4

Note:

You are advised to use Ubuntu since CentOS is discontinued.

When using Ubuntu, verify the user privilege (as the default root user is not a superuser). For details, see the notes in the following content.

Remaining free physical memory

64 GB

Note:

Registration and authentication must be completed after project deployment.

For the internal network environment that can be connected to the FanRuan cloud or the public internet environment, you are advised to authenticate registration via a public cloud. For details, see Public Cloud Authentication.

For the pure internal network environment, you need to install a registration service component on the project component server and authenticate registration via private cloud on FineOps. Therefore, you must ensure at least 2 GB of additional available physical memory on this server. For details, see New Project Registration. 

The server shall have a partition with remaining free space of more than 500 GB.

Note:

1. There must be a single partition that meets the condition.

2. The required disk space decreases if you use self-prepared components.

If you use the self-provided Elasticsearch, the required remaining free disk space on the server can be reduced by 100 GB.

If you use the self-provided external database, the required remaining free disk space on the server can be reduced by 50 GB.

For details, see Preparing the FineReport Mounting Directory.

For details, see Preparing the FineOps Server.

Note:

The mounting path cannot be /, /usr, /root, or /usr/local. You can create folders in these paths for file mounting.

Ensure that the file system of the mounting directory is configured to be automatically mounted during a boot.

Otherwise, containers may fail to access these directories, leading to data loss or application startup issues.

The mounting path cannot be a shared-use path.

Sharing the file system may cause performance degradation, file permission issues, and data inconsistency, affecting the reliability and response speed of applications running in the container.

Ensure the server has tar installed.

tar is a commonly used command-line tool for archiving and compressing files.

FineOps requires this command to decompress files.

Ensure the server has sed installed.

The sed command is used for text processing.

FineOps requires this command to process text.

Ensure the user you use can connect to the FineOps server via the SSH protocol.

Ensure the password used for the SSH connection contains no English single quotation marks ('), or the privilege will fail to be validated during deployment.

The server user responsible for deploying the project must have the necessary sudo privileges.

1. You are advised to use the root user account for project deployment and operation.

2. To use a non-root user for deployment and operation, see Linux User Privilege Explanation.

Note:

The default root user of an Ubuntu operating system is not a superuser. Ensure the user privileges meet the requirements.

At least 20 Mbps (2.5 MB/s)

Note:

1. Increase the bandwidth accordingly as the number of concurrent project sessions grows.

2. If the business databases (databases connected via data connections) and self-provided components are all on the internal network, the required public internet bandwidth can be reduced accordingly.

Component-occupied port

Component port connectivity

For details, see Confirming the FineReport Server Network.

For details, see Preparing the FineOps Server.

If the server is running the Kylin operating system, ensure that Podman is not installed on the server.

The version of runc bundled with Podman is too low and conflicts with the Docker installation managed by FanRuan, which may cause deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

Ensure that Kingsoft Antivirus is not installed on the server.

This antivirus software may trigger server connection interruptions when the dockerd command is executed, resulting in deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

It is used to install components of the FineReport project.

For details about the role of components, see Understanding the Roles of O&M Project Components.

• FineReport

• Filebeat

• OPS Agent

1. It is used to install the log and configuration components of the FineReport project.

For details about the role of components, see Understanding the Roles of O&M Project Components.

• Nginx

• MySQL (The self-provided component is supported.)

• Elasticsearch (The self-provided component is supported.)

• OPS Agent

2. It is used to install FineOps.

For details about the role of components, see Understanding the Roles of FineOps Components.

Note:

If you have installed FineOps, skip this part.

• OPS and Nginx

• Pushgateway, Prometheus, Grafana, and Alertmanager

• Elasticsearch and Skywalking OAP

• Registry (The self-provided component is supported.)

• OPS Agent

Inconsistent server time can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies.

All servers must be set to the same time zone.

Inconsistent server time zones can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies.

All servers can communicate with each other on the internal network or have open ports for access.

For details about port requirements, see the following content.

X86_64

Recommended: Ubuntu 22

Supported:

• Ubuntu 18.04.4 and later releases (Ubuntu 20.04 is not supported.)

• CentOS 7.3 to 7.9

• Red Hat 7.6 and later releases

• Rocky Linux 8.8 to 9.4

Note:

You are advised to use Ubuntu since CentOS is discontinued.

When using Ubuntu, verify the user privilege (as the default root user is not a superuser). For details, see the notes in the following content.

32 GB

Note:

Registration and authentication must be completed after project deployment.

For the internal network environment that can be connected to the FanRuan cloud or the public internet environment, you are advised to authenticate registration via a public cloud. For details, see Public Cloud Authentication.

For the pure internal network environment, you need to install a registration service component on the project component server and authenticate registration via private cloud on FineOps. Therefore, you must ensure at least 2 GB of additional available physical memory on this server. For details, see New Project Registration. 

The server shall have a partition with remaining free space of more than 300 GB.

Note:

There must be a single partition that meets the condition.

The server shall have a partition with remaining free space of more than 300 GB.

Note:

1. There must be a single partition that meets the condition.

2. The required disk space decreases if you use self-prepared components.

If you use the self-provided Elasticsearch, the required remaining free disk space on the server can be reduced by 100 GB.

If you use the self-provided external database, the required remaining free disk space on the server can be reduced by 50 GB.

For details, see Preparing the FineReport Mounting Directory.

Note:

The mounting path cannot be /, /usr, /root, or /usr/local. You can create folders in these paths for file mounting.

For details, see Preparing the FineReport Mounting Directory.

For details, see Preparing the FineOps Server.

Note:

The mounting path cannot be /, /usr, /root, or /usr/local. You can create folders in these paths for file mounting.

Ensure that the file system of the mounting directory is configured to be automatically mounted during a boot.

Otherwise, containers may fail to access these directories, leading to data loss or application startup issues.

Sharing the file system may cause performance degradation, file permission issues, and data inconsistency, affecting the reliability and response speed of applications running in the container.

tar is a commonly used command-line tool for archiving and compressing files.

FineOps requires this command to decompress files.

Ensure the server has sed installed.

The sed command is used for text processing.

FineOps requires this command to process text.

Ensure the password used for the SSH connection contains no English single quotation marks ('), or the privilege will fail to be validated during deployment.

The server user responsible for deploying the project must have the necessary sudo privileges.

1. You are advised to use the root user account for project deployment and operation.

2. To use a non-root user for deployment and operation, see Linux User Privilege Explanation.

Note:

The default root user of an Ubuntu operating system is not a superuser. Ensure the user privileges meet the requirements.

Component-occupied port

Component port connectivity

For details, see Confirming the FineReport Server Network.

For details, see Confirming the FineReport Server Network.

For details, see Preparing the FineOps Server.

If the server is running the Kylin operating system, ensure that Podman is not installed on the server.

The version of runc bundled with Podman is too low and conflicts with the Docker installation managed by FanRuan, which may cause deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

This antivirus software may trigger server connection interruptions when the dockerd command is executed, resulting in deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

It is used to install the FineReport project.

For details about the role of components, see Understanding the Roles of O&M Project Components.

• FineReport

• Filebeat

• OPS Agent

It is used to install the FineReport project.

For details about the role of components, see Understanding the Roles of O&M Project Components.

• FineReport

• Filebeat

• OPS Agent

1. It is used to install the FineReport cluster as well as log and configuration components.

For details about the role of components, see Understanding the Roles of O&M Project Components.

• Nginx

• Elasticsearch, MinIO, MySQL, and Redis (Self-provided components are supported.)

• OPS Agent

2. It is used to install FineOps.

For details about the role of components, see Understanding the Roles of FineOps Components.

Note:

If you have installed FineOps, skip this part.

• OPS and Nginx

• Pushgateway, Prometheus, Grafana, and Alertmanager

• Elasticsearch and Skywalking OAP

• Registry (The self-provided component is supported.)

• OPS Agent

The time on all servers must be synchronized, with a maximum difference of no more than 5 seconds.

Inconsistent server time can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies.

All servers must be set to the same time zone.

Inconsistent server time zones can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies.

All servers can communicate with each other on the internal network or have open ports for access.

For details about port requirements, see the following content.

Recommended: Ubuntu 22

Supported:

• Ubuntu 18.04.4 and later releases (Ubuntu 20.04 is not supported.)

• CentOS 7.3 to 7.9

• Red Hat 7.6 and later releases

• Rocky Linux 8.8 to 9.4

Note:

You are advised to use Ubuntu since CentOS is discontinued.

When using Ubuntu, verify the user privilege (as the default root user is not a superuser) and confirm that the disk type is XFS. For details, see the notes in the following content.

64 GB 

64 GB

32 GB

Note:

Registration and authentication must be completed after project deployment.

For the internal network environment that can be connected to the FanRuan cloud or the public internet environment, you are advised to authenticate registration via a public cloud. For details, see Public Cloud Authentication.

For the pure internal network environment, you need to install a registration service component on the project component server and authenticate registration via private cloud on FineOps. Therefore, you must ensure at least 2 GB of additional available physical memory on this server. For details, see New Project Registration. 

The server shall have a partition with remaining free space of more than 200 GB.

Note:

There must be a single partition that meets the condition.

The server shall have a partition with remaining free space of more than 200 GB.

Note:

There must be a single partition that meets the condition.

The server shall have a partition with remaining free space of more than 500 GB.

Note:

1. There must be a single partition that meets the condition.

2. The required disk space decreases if you use self-prepared components.

If you use the self-provided Elasticsearch, the required remaining free disk space on the server can be reduced by 100 GB.

If you use the self-provided external database, the required remaining free disk space on the server can be reduced by 50 GB.

If you use the self-provided file storage component, the required remaining free disk space on the server can be reduced by 100 GB.

Random read/write throughput (1024k) > 100 MiB/s

If you have not prepared the file service component, the FineBI MinIO component must be deployed, and the recommended disk type is XFS.

Note:

1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly.

2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly.

3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution.

For details, see Preparing the FineReport Mounting Directory.

For details, see Preparing the FineOps Server.

Note:

The mounting path cannot be /, /usr, /root, or /usr/local. You can create folders in these paths for file mounting.

Ensure that the file system of the mounting directory is configured to be automatically mounted during a boot.

Otherwise, containers may fail to access these directories, leading to data loss or application startup issues.

The mounting path cannot be a shared-use path.

Sharing the file system may cause performance degradation, file permission issues, and data inconsistency, affecting the reliability and response speed of applications running in the container.

Ensure the server has tar installed.

tar is a commonly used command-line tool for archiving and compressing files.

FineOps requires this command to decompress files.

Sed command

Ensure the server has sed installed.

The sed command is used for text processing.

FineOps requires this command to process text.

Ensure the user you use can connect to the FineOps server via the SSH protocol.

Ensure the password used for the SSH connection contains no English single quotation marks ('), or the privilege will fail to be validated during deployment.

The server user responsible for deploying the project must have the necessary sudo privileges.

1. You are advised to use the root user account for project deployment and operation.

2. To use a non-root user for deployment and operation, see Linux User Privilege Explanation.

Note:

The default root user of an Ubuntu operating system is not a superuser. Ensure the user privileges meet the requirements.

At least 100 Mbps (12.5 MB/s)

Note:

1. Increase the bandwidth accordingly as the number of concurrent project sessions grows.

2. If the business databases (databases connected via data connections) and self-provided components are all on the internal network, the required public internet bandwidth can be reduced accordingly.

Component-occupied port

Component port connectivity

For details, see Confirming the FineReport Server Network.

For details, see Confirming the FineReport Server Network.

For details, see Preparing the FineOps Server.

If the server is running the Kylin operating system, ensure that Podman is not installed on the server.

The version of runc bundled with Podman is too low and conflicts with the Docker installation managed by FanRuan, which may cause deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

Ensure that Kingsoft Antivirus is not installed on the server.

This antivirus software may trigger server connection interruptions when the dockerd command is executed, resulting in deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

It is used to install the FineReport project.

For details about the role of components, see Understanding the Roles of O&M Project Components.

• FineReport

• Filebeat

• OPS Agent

1. It is used to install the FineReport cluster as well as log and configuration components.

For details about the role of components, see Understanding the Roles of O&M Project Components.

• Nginx

• Elasticsearch, MinIO, MySQL, and Redis (Self-provided components are supported.)

• OPS Agent

2. It is used to install FineOps.

For details about the role of components, see Understanding the Roles of FineOps Components.

Note:

If you have installed FineOps, skip this part.

• OPS and Nginx

• Pushgateway, Prometheus, Grafana, and Alertmanager

• Elasticsearch and Skywalking OAP

• Registry (The self-provided component is supported.)

• OPS Agent

The time on all servers must be synchronized, with a maximum difference of no more than 5 seconds.

Inconsistent server time can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies.

All servers must be set to the same time zone.

Inconsistent server time zones can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies.

All servers can communicate with each other on the internal network or have open ports for access.

For details about port requirements, see the following content.

Recommended: Ubuntu 22

Supported:

• Ubuntu 18.04.4 and later releases (Ubuntu 20.04 is not supported.)

• CentOS 7.3 to 7.9

• Red Hat 7.6 and later releases

• Rocky Linux 8.8 to 9.4

Note:

You are advised to use Ubuntu since CentOS is discontinued.

When using Ubuntu, verify the user privilege (as the default root user is not a superuser) and confirm that the disk type is XFS. For details, see the notes in the following content.

32 GB

Note:

Registration and authentication must be completed after project deployment.

For the internal network environment that can be connected to the FanRuan cloud or the public internet environment, you are advised to authenticate registration via a public cloud. For details, see Public Cloud Authentication.

For the pure internal network environment, you need to install a registration service component on the project component server and authenticate registration via private cloud on FineOps. Therefore, you must ensure at least 2 GB of additional available physical memory on this server. For details, see New Project Registration. 

The server shall have a partition with remaining free space of more than 200 GB.

Note:

There must be a single partition that meets the condition.

The server shall have a partition with remaining free space of more than 500 GB.

Note:

1. There must be a single partition that meets the condition.

2. The required disk space decreases if you use self-prepared components.

If you use the self-provided Elasticsearch, the required remaining free disk space on the server can be reduced by 100 GB.

If you use the self-provided external database, the required remaining free disk space on the server can be reduced by 50 GB.

If you use the self-provided file storage component, the required remaining free disk space on the server can be reduced by 100 GB.

3. An extra 50 GB of disk space is required for each additional project node connected to FineOps.

If you have not prepared the file service component, the FineBI MinIO component must be deployed, and the recommended disk type is XFS.

Note:

1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly.

2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly.

3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution.

For details, see Preparing the FineReport Mounting Directory.

Note:

The mounting path cannot be /, /usr, /root, or /usr/local. You can create folders in these paths for file mounting.

For details, see Preparing the FineReport Mounting Directory.

For details, see Preparing the FineOps Server.

Note:

The mounting path cannot be /, /usr, /root, or /usr/local. You can create folders in these paths for file mounting.

Ensure that the file system of the mounting directory is configured to be automatically mounted during a boot.

Otherwise, containers may fail to access these directories, leading to data loss or application startup issues.

The mounting path cannot be a shared-use path.

Sharing the file system may cause performance degradation, file permission issues, and data inconsistency, affecting the reliability and response speed of applications running in the container.

Ensure the server has tar installed.

tar is a commonly used command-line tool for archiving and compressing files.

FineOps requires this command to decompress files.

Ensure the server has sed installed.

The sed command is used for text processing.

FineOps requires this command to process text.

Ensure the user you use can connect to the FineOps server via the SSH protocol.

Ensure the password used for the SSH connection contains no English single quotation marks ('), or the privilege will fail to be validated during deployment.

The server user responsible for deploying the project must have the necessary sudo privileges.

1. You are advised to use the root user account for project deployment and operation.

2. To use a non-root user for deployment and operation, see Linux User Privilege Explanation.

Note:

The default root user of an Ubuntu operating system is not a superuser. Ensure the user privileges meet the requirements.

At least 100 Mbps (12.5 MB/s)

Note:

1. Increase the bandwidth accordingly as the number of concurrent project sessions grows.

2. If the business databases (databases connected via data connections) and self-provided components are all on the internal network, the required public internet bandwidth can be reduced accordingly.

At least 100 Mbps (12.5 MB/s)

Component-occupied port

Component port connectivity

For details, see Confirming the FineReport Server Network.

For details, see Preparing the FineOps Server.

If the server is running the Kylin operating system, ensure that Podman is not installed on the server.

The version of runc bundled with Podman is too low and conflicts with the Docker installation managed by FanRuan, which may cause deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

Ensure that Kingsoft Antivirus is not installed on the server.

This antivirus software may trigger server connection interruptions when the dockerd command is executed, resulting in deployment failures.

Refer to the relevant document to uninstall Podman. You are advised to verify the impact of uninstallation in a non-production environment first.

FineReport

Elasticsearch deployed: Xmx+ 5 GB

Elasticsearch not deployed: Xmx+ 8 GB

Server memory - 8 GB

30 GB at most