GID and UID not working as [I] expected

[ineiti]

What happened?

I want to set the UID and GID values in the .env to the user which is running the docker compose command. But if these values are != 1000, then starting librechat fails with various permission errors.

TBH, I'm not sure I'm doing the right thing here, but I searched on internet and tried various things. I ended up setting UID and GID to 1000, which works. But this is not the user which runs librechat.

Steps to Reproduce

1. Start with a user with uid != 1000 and gid != 1000
2. set the GID and UID in the .env to the uid and gid of the user
3. sudo chmod $UID:$GID data-node images meili_data_v1.7
4. Run docker compose up

What browsers are you seeing the problem on?

No response

Relevant log output

...
chat-meilisearch  | Error: Permission denied (os error 13)
...
LibreChat         | 2024-11-14 13:13:15 error: There was an uncaught error: EACCES: permission denied, open '/app/api/logs/meiliSync-2024-11-14.log'
...

But the ~/logs directory in the user running the docker file has the ownership of the uid and gid set in the .env directory.

### Screenshots

_No response_

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

[danny-avila]

Discussion on this:
#2939 (comment)

#3647 (comment)

[ineiti]

So from what I gather:

• UID and GID only work when set to 1000 or when not set
• if they are not set, the directories are created as root, and there is a warning when starting docker-compose.yaml

To avoid confusion, I propose to hardcode the UID and GID to 1000 in the .env.example file, and add a comment with the explanation above. What do you think, @danny-avila ?

[Kevin-free]

@ineiti Same problem, how did you solve it?

[ineiti]

I use UID=GID=1000 and have a wrong user-name in my directory now... Warnings are worse than a wrong user to me.

[Kevin-free]

I've searched and tried multiple times and still have the problem “error: There was an uncaught error: EACCES: permission denied, open ‘/app/api/logs/meiliSync-2025-01-09.log’” Can you tell me what to do now? Thanks! @ineiti @danny-avila

My background info:

OS: Ubuntu 22.04

kevin$ id -u
1001
kevin$ id -g
1002

Already executed:

sudo chown -R $(id -u):$(id -g) images logs meili_data_v1.7 data-node
sudo chmod -R 755 images logs meili_data_v1.7 data-node

Current information:

drwxr-xr-x 4 lxd kevin 4.0K Jan 9 08:56 data-node
drwxr-xr-x 2 kevin kevin 4.0K Jan 9 08:49 images
drwxr-xr-x 2 kevin kevin 4.0K Jan 9 08:49 logs
drwxr-xr-x 4 kevin kevin 4.0K Jan 9 08:49 meili_data_v1.7

Start server by sudo docker-compose -f ./deploy-compose.yml up -d, and log output:

Chat-API  | 2025-01-09 08:56:07 error: There was an uncaught error: EACCES: permission denied, open '/app/api/logs/meiliSync-2025-01-09.log'

[ineiti]

I have the following. My user is:

$ id 
uid=1021(librechat) gid=1022(librechat) groups=1022(librechat),123(docker)

The directories are:

$ ls -nd images logs meili_data_v1.7 data-node
drwxr-xr-x  4 1000 1000 20480 Jan  9 14:19 data-node
drwxr-xr-x 13 1000 1000  4096 Dec 17 14:42 images
drwxr-xr-x  2 1000 1000  4096 Jan  9 13:04 logs
drwxr-xr-x  4 1000 1000  4096 May 22  2024 meili_data_v1.7

And my UID/GID settings are:

$ grep [UG]ID .env 
UID=1000
GID=1000

Which is not ideal, as the data directories do not have the same ID as the user. But because my backup runs as the root user, this is not a problem. And like this I don't get a warning when starting librechat.

[Kevin-free]

Thanks for the answer. I always had problems with GCP, but I solved it with another VPS!

[Nilegfx]

I never managed to make it work. I was excited to tryout librechat but with all solution from different issues with this permission issues I tried nothing worked so I gave up. this is so frustrating and isn't really as simple as what mentioned in this docs

[ineiti]

I never managed to make it work. I was excited to tryout librechat but with all solution from different issues with this permission issues I tried nothing worked so I gave up. this is so frustrating and isn't really as simple as what mentioned in this docs

I think if you ignore the warnings about UID and GID not set, and put your API keys in the .env, as described, it should work out-of-the-box.

The discussion here is for us nerds who don't want to have any warnings in the logs, because we look out for these things :)