github OpenListTeam/OpenList v4.1.1

latest release: beta
18 days ago

🚨 Breaking Changes

为了更好地符合容器规范(甚至哪怕是RedHat的公约性质规定),从第74号问题开始,我们就已经开始准备对容器化使用方式的重构,涉及但不限于将aria2迁移为独立镜像等。

4.1.1 版本中,我们已移除 PUID/PGID 的运行方式,并且借鉴 MariaDB 等多个知名镜像的构建方法,通过useradd 新增用户和用户组 openlist(UID: 1001,GID: 1001),并以该用户身份运行 openlist server

  • 新安装用户:理论上无需额外操作,开箱即用。
  • 已有安装用户:如有权限问题,请在宿主机为该用户进行相应授权。

由于 Docker 和 Podman 在用户命名空间映射上的差异,宿主机用户与容器用户可能不完全对应。Podman 环境下,可以通过 UIDMap 或 UserNS 映射用户。

https://doc.oplist.org/guide/installation/docker

常见问题
Q: 宿主机没有 UID 1001 的用户怎么办?
A: 不影响使用,授权时采用数字 UID 即可,无需宿主机实际存在该用户。


In order to better align with container standards (even those defined by RedHat conventions), we have started preparing a major refactor of container usage starting from Issue #74, which includes, but is not limited to, migrating aria2 to a separate image.

In version 4.1.1, we have removed the PUID/PGID method of operation and, inspired by well-known images like MariaDB, we have adopted a new build method. We now add a new user and user group called openlist (UID: 1001, GID: 1001) using useradd, and run the openlist server as that user.

  • New installations: No additional steps are needed, it’s ready to use out of the box.
  • Existing installations: If there are permission issues, please ensure the necessary authorization for the user on the host machine.

Due to differences in user namespace mapping between Docker and Podman, the host machine user and the container user may not directly correspond. In a Podman environment, you can map users using UIDMap or UserNS.

https://doc.oplist.org/guide/installation/docker

FAQ:
Q: What if the host machine doesn’t have a user with UID 1001?
A: It won’t affect usage. When granting permissions, you can use the numeric UID directly, and the actual user doesn’t need to exist on the host machine.


   🚀 Features

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

Don't miss a new OpenList release

NewReleases is sending notifications on new releases.