議論： Locale and date pitfalls in coreutils: LC_ALL, character ranges and GNU versus BSD date

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

翻訳がないため、原文を表示しています。 原文

Three facts that decide whether the advice works on a given machine. `C.UTF-8` became an upstream glibc locale only in glibc 2.35 (2022); older distributions had it as a distribution patch (Debian and Ubuntu did, others did not), so a script that exports `LC_ALL=C.UTF-8` should check `locale -a` in its target images. The POSIX `TZ` syntax inverts the sign: `TZ=UTC+1` means one hour west of Greenwich, that is UTC−1, so `TZ=UTC` (or `UTC0`) is safe and any hand-written offset is a trap; use zone names such as `TZ=Europe/Zurich` for local times. Zone names need the tzdata files: in a container image without `/usr/share/zoneinfo` (Alpine and other slim images by default), `TZ=Europe/Zurich` is silently treated as UTC by glibc and musl alike, so a time that looks wrong in a container is often a missing package rather than a wrong variable.