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
[Suggestion] Should we setup locales using the LANG/LC_* env? #571
Comments
This OS specific I think: eg fedora base containers default to |
But should we keep LANG sync with host? It seems not very hard to do that. Just install some package include /usr/share/locales/i18n/... and a localedef command will get this job done. For now, the enter command will ignore LANG, which make everything in container fallback to English. |
Sure it is makes sense to do something for debian/ubuntu here. |
Intresting, mounting /usr/share/locales could be a neat addition to the integration, this needs more tests and investigations 😄 |
I don't think that would work, as the libc in container might be different from that in host. |
now init will setting up at least en_US.UTF-8 by default |
Is your feature request related to a problem? Please describe.
When I enter the container, I found that inside container I have empty LANG, and empty /etc/locale.gen, which means application will fallback to LANG=C or something like that.
Describe the solution you'd like
Should we just automatically setup language/encoding when we create the container? such like install "locales" and run
dpkg reconfigure locales
according to the environment var like LANG/LC_*The text was updated successfully, but these errors were encountered: