Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid Locale_Name on latest image 7.2.5 #169

Open
yisraelU opened this issue Aug 20, 2024 · 1 comment
Open

Invalid Locale_Name on latest image 7.2.5 #169

yisraelU opened this issue Aug 20, 2024 · 1 comment

Comments

@yisraelU
Copy link

yisraelU commented Aug 20, 2024

Environment

  • docker-redis-cluster version: 7.2.5
  • docker compose : v2.26.1-desktop.1

Service declaration in docker compose file

  RedisCluster:
    restart: always
    image: grokzen/redis-cluster:7.2.5
    ports:
      - "30001:30001"
      - "30002:30002"
      - "30003:30003"
      - "30004:30004"
      - "30005:30005"
      - "30006:30006"
    environment:
      - IP=0.0.0.0
      - INITIAL_PORT=30001
      - DEBUG=true
     ```


### Steps to Reproduce

1. docker-compose up


Expected : The container to run with redis-server services running per cluster config


Happened: The container runs and I can see all 6 redis-server instaces start up and they all fail with 
```RedisCluster-1  | 67:M 20 Aug 2024 16:54:16.502 # Failed to configure LOCALE for invalid locale name.

I can also see this warning upon startup

I believe that is the cause .

The locale is not successfully installed at

RUN locale-gen en_US.UTF-8

If I exec into the container and run the same locale-gen command it fails.

To rectify it , I needed to run this instead

echo "en_US.UTF-8 UTF-8" >> /etc/locale.gen
echo "LANG=en_US.UTF-8" > /etc/locale.conf
locale-gen en_US.UTF-8

Once running that and restarting the container , everything worked correctly.

Summary: locale-gen en_US.UTF-8 is failing because it is not found in the config files, therefore this results in the servers not starting

@lindelius
Copy link

We have the same issue, and the above fix did seem to solve it for us, as well. Thanks @yisraelU

Any chance to get this fixed in the main image? @Grokzen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants