Can you mount a cloud drive to your NAS and use it as a local drive? I linked my Alibaba Cloud drive to Feiniu, and the TV broadcast 4K directly, with a monthly payment in advance

last month, I finished writing storage pool cleaning, and a 4TB disk cleared out over 400GB. I knew I wouldn't last half a year—the photo library would grow by 60-70GB a year, and the next 4K movie would easily be 50-60GB. My cousin enlightened me with one sentence: Isn't your Alibaba Cloud drive just freeloading 2TB? Just hang it on your NAS and use it as a local drive, isn't that it?

At first, I thought this idea was a bit off: NAS users and cloud storage users have always been two different groups. I used to calculate private cloud and public cloud accounts. Once you get hands-on, you'll realize that cloud drive mounting has gone all the way in recent years—playing 4K on the TV directly from the cloud drive, and the NAS doesn't need to store a single byte. But after a month of use, the pitfalls are real—it's no exaggeration to discourage half the people.

first clarify three paths: CloudDrive 2, OpenList, and strm each manage a segment

Before getting started, I spent two days browsing the Feiniu forum and Enshan and found that under the term "cloud drive mounting," there are actually three completely different paths. Let's first identify before acting:

to say a bit more about the origin of OpenList: The long-established tool AList was popular across the internet a few years ago, but its maintenance pace has clearly slowed in recent years. The community forked OpenList to continue updating, and the cloud drive driver has followed up faster. Now, almost all new PCs are pushing for it. Existing AList users don't need to rush to migrate; new installers can start directly from OpenList.

I ultimately chose CloudDrive 2 to run Alibaba Cloud Container Management for daily use. The strm set wasn't available—my library isn't big enough yet, so I was too lazy to add another layer of service.

how I set it up: Docker takes ten minutes, and the system gains an extra 'disk'

There's not much to say about the deployment itself—it's just the standard Docker process. I've written about the basic concepts in Feiniu Docker Beginner's and a Complete Docker Getting Started . You can't find this mirror in Feiniu App Center, so you have to pull it up yourself in Docker. There are two main points where things really go wrong:

First, CloudDrive2's containers need to be enabled in privileged mode, which can only be used with FUSE to disguise the cloud drive as a disk. Without privileges, it simply can't start up. The mount point is by default in the container at /media/cloudnas. Remember to map this path to the host, otherwise if you attach it, you won't see it in File Management.

second, it writes the configuration inside the container by default. Once the container is deleted, all login cloud accounts disappear, and you have to scan a code to start over. First, map it out with a configuration directory—this is the general rule for all container deployments. After

it up, go to the management page in your browser, scan the QR code to log in to Alibaba Cloud Drive, and a mounted scroll will immediately appear in Feiniu's file management section. Inside is my 2TB cloud drive, with a directory structure exactly the same as the web version. It's even easier on the TV side: the mount point is shared with the SMB. Add this path in Kodi, and movies from the cloud drive can be played directly by clicking. It's the same idea as I wrote before about TV directly connected to NAS to play movies, except the drive is now cloud-based.

playback is the real test: whether 4K works depends on 302 redirects and benefit packages

Here's a counterintuitive fact: when playing cloud drive videos on a mounted drive, the data actually doesn't flow through NAS.

to explain this mechanism: the TV asks the NAS, "Give me this file," the NAS turns around and asks for the cloud storage download link, and the cloud drive replies "The item is in my CDN data center, building number xxx, you can get it yourself"—this step is a 302 redirect. The NAS only handed over a note the whole time; the real large files went straight from the cloud drive server to the TV. So the N100's performance isn't a bottleneck at all; whether it lags depends entirely on whether the cloud drive delivers it quickly.

my one-month test experience: 1080P online video source bitrates are generally around 8MB, so you can play casually and drag the progress bar for two or three seconds before connecting; For 4K original discs with 50-60 Mbps bitrate, it all depended on how the cloud drive was at the time—smooth late at night, always spinning during rush hour. The root of this "mood-depending" issue is the toughest hurdle: Alibaba Cloud Disk's third-party benefits package. In mid-

2024, Alibaba Cloud Drive 6.0 launched the "Third-Party Application Benefits Package." Simply put, if you mount with third-party tools like CloudDrive 2 or OpenList, the benefits count separately; in mid-2024, Alibaba Cloud Drive 6.0 launched the "Third-Party Application Benefits Package." Simply put, if you mount with third-party tools like CloudDrive 2 or OpenList, the benefits count separately:

, third-party platforms offer maximum standard definition and download speed limits. In my tests, single-thread speeds range from 100KB to 500KB per second, and the player running 16 threads is about 9MB per second. Converted to 72MB bandwidth—1080P is just barely enough, 4K is purely a matter of luck. If you buy it, you get high-speed channels and high-definition video, but according to the flow meter quota, once the quota runs out, it still reverts to the original state. Some complain that after buying the benefit package, data drops rapidly—a single 4K package costs dozens of gigabytes; There are even more frustrating complaints: the marketing claims WebDAV exists, but in reality, WebDAV can only be downloaded and not shared.

my calculations are straightforward: freeloaders only list 1080P dramas and documentaries, and even without buying the benefits package, it's enough; For 4K original drive users, the data allowance can't last a month; it's better to save that money to buy a hard drive. The speed of cloud drive is never for you—it's for its own client.

the mount drive is not a local drive, don't point upward to the download or docker directory

the moment you mount it, it looks exactly like the local drive, but essentially, it's a "borrowed" directory. There are three things you must never do:

First, don't point the qBittorrent download directory to the mount drive. The downloader uses multithreaded frequency, uses the cloud drive upload interface, and the privilege package traffic burns at double speed, which can easily trigger cloud drive risk controls. My downloader still honestly writes to the local SSD and picks the niche files for transferring to cloud drives. I did this habit in my about downloaders.

Second, don't place the mount disk in the data directory of the Docker container. Things like QB configuration and photo album databases need to be read and written locally at high frequency random times. If the cloud drive interface shakes once, the container crashes. The mounting drive only stores the finished files that are 'read more and write less.'

Third, don't expect it to enter the storage pool. ext4 and Btrfs manage local block devices; the mount drive is just a guest for them, with snapshots, deduplication, and quotas all covered. If you want to expand, plugging in a USB storage drive is more reliable than this one. I've tested it separately.

interfaces change at a moment's notice; AList is a cautionary tale

The real problem with these tools isn't the code, but the policy. AList was very popular back then, but maintenance has slowed down now; Alibaba Cloud Drive has also tightened third-party interfaces, causing many users to disable mounting without delay. If a cloud drive party ever dislikes a third party, speed limits, protocol changes, or interface closures are all just notices—there's no room to negotiate.

so I have a clear positioning for this mounting plate: an extension of the warehouse, not a replacement for the warehouse. shows you delete after just one watch, or leftover movies stored on cloud drives; Photos and work documents—things that would hurt if lost—still stick to 3-2-1. As a rule, I wrote in my backup that cloud only picks a few small items that really need to be stored in different locations. Nut Cloud is for this.

who deserves trouble, and who should be spared

Here's the step: first figure out what clarity you mainly care about, free users test OpenList first, then switch to CloudDrive 2 if web management is troublesome, buy the benefits package as needed and don't hoard, and back up important data as needed. My current usage is to have about 200 niche movies lying on the drive, Kodi for the TV, and local 4TB for photos and next month's new releases—each doing what they do best. Only then is the money and capacity truly well spent.