We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have read the documentation. 我已经阅读了文档。
I'm sure there are no duplicate issues or discussions. 我确定没有重复的issue或讨论。
I'm sure it's due to AList and not something else(such as Network ,Dependencies or Operational). 我确定是AList的问题,而不是其他原因(例如网络,依赖或操作)。
AList
Dependencies
Operational
依赖
操作
I'm sure this issue is not fixed in the latest version. 我确定这个问题在最新版本中没有被修复。
v3.41.0
似与此无关
因为新挂载为本机存储的一些目录需要用一特定的宿主机用户访问,因此调整了容器运行时的PUID和PGID(以前是0,现在是另一个数),此外无其它更改。
修改设置后容器本身可启动,alist工作正常,但aria2c不能自动启动。
原因似与那个PUID有关:/entry.sh里启动aria2c的那句exec su-exec ${PUID}:${PGID} nohup aria2c ..... ,如果设置了非0的PUID,则在容器里这个PUID的用户会因无法访问 /root/.aria2/aria2.conf 而导致aria2c运行失败。
但是我需要那个PUID访问宿主机文件……我该如何解决呢?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Please make sure of the following things
I have read the documentation.
我已经阅读了文档。
I'm sure there are no duplicate issues or discussions.
我确定没有重复的issue或讨论。
I'm sure it's due to
AList
and not something else(such as Network ,Dependencies
orOperational
).我确定是
AList
的问题,而不是其他原因(例如网络,依赖
或操作
)。I'm sure this issue is not fixed in the latest version.
我确定这个问题在最新版本中没有被修复。
AList Version / AList 版本
v3.41.0
Driver used / 使用的存储驱动
似与此无关
Describe the bug / 问题描述
因为新挂载为本机存储的一些目录需要用一特定的宿主机用户访问,因此调整了容器运行时的PUID和PGID(以前是0,现在是另一个数),此外无其它更改。
修改设置后容器本身可启动,alist工作正常,但aria2c不能自动启动。
原因似与那个PUID有关:/entry.sh里启动aria2c的那句exec su-exec ${PUID}:${PGID} nohup aria2c ..... ,如果设置了非0的PUID,则在容器里这个PUID的用户会因无法访问 /root/.aria2/aria2.conf 而导致aria2c运行失败。
但是我需要那个PUID访问宿主机文件……我该如何解决呢?
The text was updated successfully, but these errors were encountered: