[BUG] - Setting PUID/PGID environment variables with the docker container have no effect

[anoadragon453]

First Check

• This is not a feature request.
• I added a very descriptive title to this issue (title field is above this).
• I used the GitHub search to find a similar issue and didn't find it.
• I searched the Mealie documentation, with the integrated search.
• I already read the docs and didn't find an answer.
• This issue can be replicated on the demo site (https://demo.mealie.io/).

What is the issue you are experiencing?

Attempting to set the PUID / PGID environment variables for the mealie docker image have no effect. When execing into the container, I see that the mealie process is still running as root (uid 0).

This appears to be due to the change_user function being commented out in #2539:

mealie/docker/entry.sh

Lines 44 to 46 in ca9f66e

	# change_user
	init
	GUNICORN_PORT=${API_PORT:-9000}

Was this intentional?

Steps to Reproduce

1. Run PUID=555 PGID=555 docker run ghcr.io/mealie-recipes/mealie:v1.0.0-RC2
2. Run docker exec -it <mealie-container-id> /bin/bash
3. Inside the container, install ps: apt update && apt install procps -y
4. View the container's running processes with ps aux
5. See that /app/run.sh and python are still running as root, when they should be running as abc:

/# ps aux
USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root           1  0.0  0.0   2576  1408 ?        Ss   09:22   0:00 /bin/sh -c $MEALIE_HOME/run.sh
root           2  0.0  0.0   2576  1536 ?        S    09:22   0:00 /bin/sh /app/run.sh
root          10  0.9  4.0 371316 157124 ?       Sl   09:23   0:08 /opt/pysetup/.venv/bin/python /opt/pysetup/.venv/bin/uvicorn mealie.app:app --ho
root          16  0.0  0.0   4608  3584 pts/0    Ss   09:28   0:00 /bin/bash
root         182  0.0  0.1   8480  4352 pts/0    R+   09:38   0:00 ps aux

Please provide relevant logs

N/A

Mealie Version

ghcr.io/mealie-recipes/mealie:v1.0.0-RC2

Deployment

Docker (Linux)

Additional Deployment Details

No response

[zwimer]

This is a must-have for docker containers exposed to a network!