You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was trying out the docker image and setting up docker-compose and kept getting errors about access. That OS distro is RHEL 8.
It appears that "you" use UID 999 (and 1000 for some reason) and GID 999 for the service inside the docker image.
That overlaps with the default <1000 is system user and groups only.
UID 999 is the systemd-coredump user managed and installed by systemd
GID 999 is the input group (I don't know which one uses it on a server).
Could you fix this mixup of valkey being a system service maintained by the distros and make the UID and GID larger than 1000 which is also the advised method for non system accounts. E.g. 65535 for both would be ideal as it is the default "nobody" group on systems.
The text was updated successfully, but these errors were encountered:
I was trying out the docker image and setting up docker-compose and kept getting errors about access. That OS distro is RHEL 8.
It appears that "you" use UID 999 (and 1000 for some reason) and GID 999 for the service inside the docker image.
That overlaps with the default <1000 is system user and groups only.
You set the UID/GID's here: https://github.com/search?q=repo%3Avalkey-io%2Fvalkey-container%20999&type=code
On e.g. RHEL 8 then
systemd-coredump
user managed and installed by systemdinput
group (I don't know which one uses it on a server).Could you fix this mixup of valkey being a system service maintained by the distros and make the UID and GID larger than 1000 which is also the advised method for non system accounts. E.g. 65535 for both would be ideal as it is the default "nobody" group on systems.
The text was updated successfully, but these errors were encountered: