To mount a bucket, the following preparations are required.
A Tencent Cloud Lighthouse server, ensuring that the /tmp cache directory under the server's system disk has at least 10GB of free space.
a same-region Tencent Cloud LighthouseCOS(LHCOS) bucket.
Feature Overview
Users can mount a bucket to a Lighthouse server in the Lighthouse console to create a mount point. Each mount point consists of four elements: server, server mount directory, bucket, and bucket mount directory.
After successful mounting, the data between the server's mount directory and the bucket's mount directory is fully synchronized, users can use the COS bucket space like a local disk.
Note:
The mount feature only supports Linux systems (excluding custom images). For details, see Usage Restrictions.
Usage Steps
Mount the bucket
Option 1: Mount via the bucket page
1. Go to the COS page in the console, and select the bucket to be mounted. Go to the bucket details page, and select Mount Server.
2. Click Mount to Server to create a mount point. Enter the following information:
Select a same-region Lighthouse server.
Bucket mount directory: Enter the bucket mount directory. Note that the path should start with /, for example /aaa.
Server mount directory: Enter the server's local directory, which will serve as the local mount directory (for example, /home/lighthouse/lhcos-data). No files should exist in this directory, or you can enter a non-existent local directory.
Before creating a mount point, you must grant the current Lighthouse server permission to anonymously access the bucket mount directory. For details, see Mount Authorization.
Advanced parameters (Optional).
Concurrency: The number of concurrent transfers for mounting can be appropriately adjusted based on the server's CPU cores. If the server has N CPU cores, the default recommended value is max(10, 2*N).
Chunk size: During mount transfers, large files use chunked upload with a default chunk size of 10MB. Since chunked upload supports a maximum of 10,000 chunks, you can increase this parameter if you need to transfer large files exceeding 100GB.
3. Click Confirm to start mounting. The progress of the current mount task can be viewed through Mount Status. Click the
icon on the right to refresh the status.
Note:
Mounting is an asynchronous task that may take a few seconds to 1 minute to complete. You can view the progress of the current mount task through the mount status.
Method 2: Mounting can be performed on the Lighthouse server page
1. Go to the server page in the console, select the server that needs to be mounted. On the server details page, choose COS > Mount Bucket.
2. Click Mount Bucket to start creating a mount point. Fill in the following information:
Select a bucket in the same region.
Bucket mount directory: Enter the bucket mount directory. Note that the path must start with /, for example /aaa.
Server mount directory: Enter the server's local directory, which will serve as the local mount directory (such as /home/lighthouse/lhcos-data). This directory must not contain any files, or you may enter a non-existent local directory.
Before creating a mount point, you must grant the current Lighthouse server permission to anonymously access the bucket mount directory. For details, see Mount Authorization.
Advanced parameters (Optional).
Concurrency: The concurrency for mount transfers can be adjusted appropriately based on the number of server CPU cores. If the server has N CPU cores, the default recommended value is max(10, 2*N).
Chunk size: During mount transfers, large files use chunked upload with a default chunk size of 10MB. Since chunked upload supports a maximum of 10,000 chunks, you can increase this parameter if you need to transfer large files exceeding 100GB.
3. Click OK to start mounting. You can view the progress of the current mount task through Mount Status. Click the
button on the right to refresh the status.
Note:
Mounting is an asynchronous task that may take from a few seconds to 1 minute. You can view the progress of the current mount task through the mount status.
View files
After mounting is completed, log in to the Lighthouse server and enter the server mount directory. At this point, the contents of the bucket mount directory and the server mount directory are synchronized and identical.
Enter the server mount directory and write a new file.
cd /lhcos-data
echo111111> test.txt
Go to the console and enter the mount directory corresponding to the bucket. You will find that test.txt has been written to it.
Return to the server mount directory and delete the test.txt file.
Note:
After deletion, data cannot be recovered. Please proceed with caution.
cd /lhcos-data
rm ./test.txt
Go to the console and access the bucket's mount directory. The corresponding file is no longer present.
Modify the mount configuration
Note:
If you need to modify the mount server, mount bucket, or adjust chunk parameters and concurrency parameters, you must remove the mount and remount it.
In the mount configuration, click Edit to modify the server mount directory and bucket mount directory. Changes to the mount configuration take some time to take effect. You can check whether the modification is complete via the mount status.
Remove the mount
In the mount configuration, click Remove to remove the mount. When the mount point is removed, the mount authorization will also be deleted. The server will be unable to view or synchronize files, but the files will not be deleted and will continue to be stored in the bucket.
Default Shared Bucket and Shared Storage Value Resource Pack
Note:
By default, shared buckets can only be created when a Lighthouse instance is newly purchased.
Default shared bucket
Default Shared Bucket is a special type of LHCOS bucket. Servers within the same region share the storage space of this bucket, with a fixed naming format: lhcos-XXXXX-${appid}. Here, XXXXX represents a 5-character random string, and appid refers to the current account's appid.
When a user purchases a new server on the Lighthouse instance purchase page, if the user selects One-Click Mount Shared Bucket or purchases the Shared Storage Value-Added Package on the purchase page. After the Lighthouse server purchase is completed, the default shared bucket in the same region will be automatically mounted. The mount directory follows the following format:
Server mount directory (default): /lhcos-data
Bucket mount directory (default): /lhcos-data
If multiple servers are purchased at once, they will share the same mount directory of the default bucket, effectively sharing a common storage space. If additional servers are purchased in the same region later, they can also be mounted to the same default bucket by default. If you do not wish to share the mount space or need to modify the server or bucket mount directory, you can adjust the mount configuration or remove the mount on the bucket mount page or server mount page respectively.
Shared Storage Value-Added Package
For users who have never purchased a Lighthouse Container Object Storage (LHCOS) resource package, when purchasing a Lighthouse server on the purchase page, they can additionally buy a CNY 1 Shared Storage Value Storage Package (including 10GB of standard storage capacity and 1GB of public network downstream traffic). After successful purchase of the CNY 1 package, the system will automatically perform the following operations:
The LHCOS service and corresponding service roles will be activated for you.
Create a Default Shared Bucket in the server's region, with a fixed naming format: lhcos-XXXXX-${appid}. Here, XXXXX represents a 5-character random string, and appid refers to the current account's appid.
The servers newly purchased in this order will automatically mount the Default Shared Bucket.
Server mount directory (default): /lhcos-data
Bucket mount directory (default): /lhcos-data
Use Limits
1. A single server can create up to 10 mount points. Different mount points can mount the same bucket, but the bucket mount directories must be distinct.
2. The server mount directory does not support the use of symbolic links. When a mount point is created, the server mount directory must be empty and must not contain any existing local files.
3. The system disk of the server must have at least 10GB of space available in the /tmp cache directory.
4. The mount feature only supports servers with Linux systems (excluding custom images). The specific support status for various Linux system images is as follows.
Type
Image type
Whether Supported
System image
CentOS 7.6
Supported
CentOS Stream 8
Supported
CentOS Stream 9
Supported
OpenCloudOS 8
Supported
OpenCloudOS 9
Supported
Ubuntu Server 18.04.1 LTS
Supported
Ubuntu Server 20.04 LTS
Supported
Ubuntu Server 22.04 LTS
Supported
Ubuntu Server 24.04 LTS
Supported
Debian 10.2
Supported
Debian 11.1
Supported
Debian 12.0
Supported
Application Templates
Baota Linux Panel - OpenCloudOS 9
Supported
WordPress - CentOS 7.8
Supported
Halo Website Building - Ubuntu Server 22.04 LTS 64bit
Supported
WooCommerce - CentOS 7.6
Supported
LAMP - Ubuntu Server 24.04 LTS 64bit
Supported
OpenFaaS - CentOS 7.6
Supported
SRS Audio-Video Server - Ubuntu Server 20.04 LTS
Supported
Typecho - CentOS 7.9
Supported
Cloudreve - CentOS 7.8
Supported
Matomo - CentOS 7.6
Supported
Node.js - OpenCloudOS Server 9
Supported
Cloud Studio IDE - CentOS 7.6
Supported
Theia IDE - Ubuntu Server 18.04.1 LTS
Supported
Pterodactyl Panel - Ubuntu Server 22.04 LTS
Supported
Palworld Ubuntu - Ubuntu Server 22.04 LTS
Supported
Docker CE - Ubuntu Server 24.04 LTS
Supported
K3s - Ubuntu Server 24.04 LTS
Supported
1Panel Linux - Ubuntu Server 22.04 LTS
Supported
LobeChat - Ubuntu Server 22.04 LTS
Supported
Dify -Ubuntu Server 22.04 LTS
Supported
ChainMaker - CentOS 7.6
Supported
Interactive Live Streaming Room Service - CentOS 7.9
Supported
Lightwings - CentOS 7.9
Supported
Container image
OpenCloudOS8-Docker26
Supported
CentOS7.6-Docker26
Supported
Ubuntu22.04-Docker26
Supported
Debian12-Docker26
Supported
CentOSStream9-Docker26
Supported
Custom Image
Not supported at all
\\
FAQs
Mount Authorization
Before mounting a bucket, you must grant the current Lighthouse server permission for anonymous access to the bucket mount directory. After authorization is confirmed, the corresponding directory can be accessed anonymously on this Lighthouse server. When the mount configuration is modified, if it involves changing the bucket mount directory, the scope of authorization will also be updated to the new mount directory. When the mount is removed, the corresponding authorization will also be removed.
Mount status abnormal
On the bucket mount configuration page or server mount configuration page in the console, you can view the mount status. The mount status can be divided into three types:
Mount Abnormal: The mount status becomes abnormal due to reasons such as failed installation of the mount tool or the mount point not running. In this case, you can try removing the mount and remounting to fix the issue.
Mount Successful: Indicates that the mount point is running properly.
Mounting: Indicates that the mount task is being performed. Please wait for a while.
Possible causes of mount abnormalities
1. Insufficient disk space caused mount failure
Mount tools use disk file caching for both uploads and downloads. When the available space in the /tmp directory is less than 10GB, it will cause mount failure.
2. The server mount directory is a symbolic link.
The server mount directory must be an actual directory. Mounting to such as symbolic links, shortcuts, and so on, will result in mount failure.
3. server mount directory already contains local files.
When a mount is performed, if the server mount directory is not empty and contains files, the mount operation will report an error.
4. Server is currently powered off.
The server must currently be in a powered on state for the tat agent and mount tool to function properly; otherwise, performing the mount will fail, and mounted points will display an abnormal mount status.
5. Server
has not installed tat agent or tat agent is not online.
Performing mounts and detecting the status of mount points both depend on tat agent. If the server does not have tat agent installed or tat agent is offline, mount operations will fail, and mounted points will display an abnormal mount status.
Solution: Go to the server details page to confirm whether TAT is online. If TAT is offline or not installed, refer to Installing the TAT Client.
6.
Mount point not found (
Not found the mount path
).
Possible causes: The mount tool exited abnormally, or the user manually uninstalled it via the command line. It is recommended to remove the mount and attempt to remount.
A server can mount a maximum of buckets
A single server can create up to 10 mount points. Different mount points can mount the same bucket, but the bucket mount directories must be distinct. In other words, the tuple (server ID, storage bucket, bucket mount directory) must be unique.
Can it support mounting COS buckets?
The current automatic mount feature in the Lighthouse console only supports mounting buckets from the Lighthouse Cloud Object Storage (LHCOS) service to Lighthouse servers. To mount a COS bucket to a Lighthouse server, manually install the GooseFS-Lite tool and complete the mount process via the command line. For details, see GooseFS-Lite Tool.
