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
In the amazon/aws-lambda-ruby:3.3 Docker image, a non-existent locale is set for LANG, causing the default encoding of Ruby strings to become US-ASCII
#167
Open
pocari opened this issue
Jun 21, 2024
· 0 comments
In the amazon/aws-lambda-ruby:3.3 Docker image, a non-existent locale is set for LANG, causing the default encoding of Ruby strings to become US-ASCII. Is this intentional?
% docker run --rm -it --entrypoint sh amazon/aws-lambda-ruby:3.3
sh-5.2# locale
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
sh-5.2# ruby -e 'p "string_value".encoding'
#<Encoding:US-ASCII>
Due to this issue, when using Ruby 3.3, there were cases where an 'invalid byte sequence' error occurred when handling the contents of a file with UTF-8 strings from external sources. Therefore, I am addressing this by setting LANG to the existing UTF-8 encoding C.UTF-8 during the Docker build to ensure UTF-8 support.
% docker run --rm -it --entrypoint sh amazon/aws-lambda-ruby:3.3
sh-5.2# locale -a
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_COLLATE to default locale: No such file or directory
C
C.utf8
POSIX
The text was updated successfully, but these errors were encountered:
In the amazon/aws-lambda-ruby:3.3 Docker image, a non-existent locale is set for LANG, causing the default encoding of Ruby strings to become US-ASCII. Is this intentional?
The behavior in the 2.7 image
The behavior in the 3.3 image
Due to this issue, when using Ruby 3.3, there were cases where an 'invalid byte sequence' error occurred when handling the contents of a file with UTF-8 strings from external sources. Therefore, I am addressing this by setting LANG to the existing UTF-8 encoding C.UTF-8 during the Docker build to ensure UTF-8 support.
The text was updated successfully, but these errors were encountered: