What caused /usr/bin/sh setlocale: LC_ALL: cannot change locale (en_US.UTF-8) on Linux?

[wli3]

This is a question. I think you might have a better answer. Do you know what caused the error /usr/bin/sh setlocale: LC_ALL: cannot change locale (en_US.UTF-8) on Linux?
https://dev.azure.com/dnceng/public/_build/results?buildId=386114&view=logs

It happens when the docker image does not have the correct locale. However I don't know where in the stack this error happens, and what is the solution since so far I cannot make SDK work on Fedora 30

[dagood]

Related PR: dotnet/installer#5186 (comment)

@crummel, you mentioned fixing something like this in dotnet/source-build#1014, but I don't see what it was, do you have some more info on this? Is there something that could be applied to dotnet-buildtools-prereqs-docker to help everyone?

/cc @MichaelSimons

[wli3]

I am having the same issue on Debian stretch dotnet/installer#5186
@tannergooding I am trying my luck. Do you know who may know this issue?

[crummel]

We used an extremely brute-force approach: https://github.com/dotnet/source-build/blob/1bcf041037537b46508328fa916a77bc9e20855f/build.sh#L29. It's definitely not a good fix, but I think it could be temporarily applied anywhere.

[wfurt]

Assuming given language is available it tricky. I've see LANG=C in past to force Posix (and only available on Alpine). But that could break .NET prior to 3.0 as it would assume case-sensitive strings even if asked explicitly for case-insensitive comparison)

For now it may be worth of updating documentation to get expected locale prior of building.

[wli3]

So this is a lacking locale issue? And the right fix should be apt-get install the missing locale?

[MichaelSimons]

In the scope of Fedora 30, @omajid provided some additional context here with some suggested fixes

There's two fixes for this, as far as I can tell:

Use a C locale. C/C.UTF-8/POSIX work out of the box
Install the language pack for the non-C locale. That's what glibc-langpack-en does.

[MichaelSimons]

@wli3 - Have your questions been sufficiently answered? Can this issue be closed?

[wli3]

Thanks