docker-Container 的xhofe/alist:latest使用占用cpu高

[80718666]

Please make sure of the following things

• [X] I have read the documentation. 我已经阅读了文档。

• [X] I'm sure there are no duplicate issues or discussions. 我确定没有重复的issue或讨论。

• [X] I'm sure it's due to AList and not something else(such as Network ,Dependencies or Operational). 我确定是AList的问题，而不是其他原因（例如网络，依赖或操作）。

• [X] I'm sure this issue is not fixed in the latest version. 我确定这个问题在最新版本中没有被修复。

AList Version / AList 版本

lastest

Driver used / 使用的存储驱动

One

Describe the bug / 问题描述

用docker Container 构建alist '''version: '3.3'
services:
alist:
image: 'xhofe/alist:latest'
container_name: alist
network_mode: host
volumes:
- '/volume1/docker/alist:/opt/alist/data'
environment:
- PUID=0
- PGID=0
- UMASK=022
restart: unless-stopped'''

构建后使用时cpu一直占用率高，关闭手机播放器软件后，alist也一直在工作，而且cpu一直占用很高，视乎有些不正常。

Reproduction / 复现链接

Config / 配置

123

Logs / 日志

[welcome[bot]]

Thanks for opening your first issue here! Be sure to follow the issue template!

[80718666]

电报群有人说可能是本地回环导致，可是要怎样修复和改善这个问题呢，因为也需要用到本地回环访问。。

[woshichenghaibo]

我的占15%左右。

[msycn]

解决方法找到了: 不用Docker版

[woshichenghaibo]

那用什么版本？怎么安装？

---

发件人: msycn @.> 发送时间: 2024年3月26日 22:36 收件人: alist-org/alist @.> 抄送: woshichenghaibo @.>; Comment @.> 主题: Re: [alist-org/alist] docker-Container 的xhofe/alist:latest使用占用cpu高 (Issue #6205)

解决方法找到了: 不用Docker版

― Reply to this email directly, view it on GitHubhttps://github.com/alist-org/alist/issues/6205#issuecomment-2020605259, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATGWDIKL5FVYH56V5ZYF6GTY2GBVTAVCNFSM6AAAAABESKDT7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRQGYYDKMRVHE. You are receiving this because you commented.Message ID: @.***>

[msycn]

那用什么版本？怎么安装？ … 一键安装脚本 curl -fsSL "https://alist.nn.ci/v3.sh" | bash -s install

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

Hello @, this issue was closed due to inactive more than 52 days. You can reopen or recreate it if you think it should continue. Thank you for your contributions again.