Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

locale_get_display_name does not work as expected by default in Alpine Linux 3.16 based PHP images

Open
#1,302 9 comments 17 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, dockerfile, php

Research direction

Start with the Alpine-based PHP image definitions and the APK packages they install. Reproduce locale_get_display_name('ja', 'ja') in an Alpine 3.16-based PHP image, then verify the selected package behavior and document or implement the maintainer-approved default for full ICU locale data.

Written by the indexing model from the issue text.

Description

question

The latest PHP images based on Alpine Linux now use Alpine Linux v3.16.

In v3.16, Alpine Linux has split the ICU package in two: icu-data-en and icu-data-full.

Only the icu-data-en package is now installed by default. The Alpine Linux changelog mentions this as well:

icu-libs only installs icu-data-en. If additional language support is required, icu-data-full needs to be installed manually. 
# apk list | grep -i icu
icu-libs-71.1-r2 x86_64 {icu} (MIT ICU Unicode-TOU) [installed]
icu-data-en-71.1-r2 x86_64 {icu} (MIT ICU Unicode-TOU) [installed]

This results in the following code not working as expected:

<?php

echo locale_get_display_name('ja', 'ja');

This now yields the output Japanese instead the expected 日本語. Other locale-related methods will probably also be affected.

Would the Alpine-based PHP images want to include the icu-data-full package by default? Or is this package expected/intended to be not installed by default?

See

Dominant language
Dockerfile
Stars
4k
Forks
2k
Avg merge
5d 21h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from docker-library/php

All issues in docker-library/php

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.