docker log show chown operation not permitted (Bug report)

[supermayx]

Trilium Version

0.59.4

What operating system are you using?

Other Linux

What is your setup?

Server access only

Operating System Version

openwrt docker

Description

I was working with ver.0.50.2 on docker without any issue.
Then I noticed the newer version is 0.59.4, so I tried to upgrade it.
all I get is these log:
...................
chown: /home/node/trilium-data/sessions/iTx1zqDRR4XbSKbSrP0UUqPeHclqKakN.json: Operation not permitted
chown: /home/node/trilium-data/sessions/IUPfWjDbKNPZlj18jImADQrtUSVvguaL.json: Operation not permitted
chown: /home/node/trilium-data/sessions/iXGHRyDMCZcclOR4VKPRmw7nv5tXl_sh.json: Operation not permitted
chown: /home/node/trilium-data/sessions/ixH7LOsZNmOxTY-Klm3AmMftkdmxnaFX.json: Operation not permitted
chown: /home/node/trilium-data/sessions: Operation not permitted
chown: /home/node/trilium-data/sessions: Operation not permitted
chown: /home/node/trilium-data/session_secret.txt: Operation not permitted
chown: /home/node/trilium-data: Operation not permitted
chown: /home/node/trilium-data: Operation not permitted
su-exec: setgroups: Operation not permitted
...............

I tried to add env to set USER_UID, USER_GID, to 0, 1000, or 1001, all with no luck.
Then I tried older version 0.52.3, same issue.
Then I started the original 0.50.2, working smoothly.

So, can anyone please tell me how to fix this?
Thanks!

Error logs

No response

[supermayx]

while setting USER_UID=1001 in env, the log says:
usermod: user node is currently used by process 1
No USER_UID specified, leaving 1000
groupmod: /etc/group.9: Permission denied
groupmod: cannot lock /etc/group; try again later.
No USER_GID specified, leaving 1000

while setting USER_UID=0 in env, the log says:
usermod: UID '0' already exists
No USER_UID specified, leaving 1000
groupmod: GID '0' already exists
No USER_GID specified, leaving 1000

[supermayx]

Found a clue in v0.52.2 release note saying: "Note that Docker image now requires root permissions to run, #2907"

But it is just too hard for a muggle like me to figure out how to do it, can anyone show a hint in English? Thanks!

[soulsands]

I'm not sure about the issue, but you can use the command "whoami" to see if you are logined as root user, if the result is not 'root', that might be the reason.

[supermayx]

@soulsands
Thanks for the kind reply, where should I use the command?
I can connect to the server via ssh, with root user, so I guess the answer to "whoami" is obivious.
And I use portainer to manage my containers mostly, I'm not sure which user it is. and not sure where to input the whoami command.

I'll try using command line to install and run the container in SSH, hope it will work, and update the result later.
Thanks.