Get rid of global env variable DEBIAN_FRONTEND #64

New Issue

AtHeartEngineer · 2025-07-08T08:38:48-04:00

AtHeartEngineer commented

2025-07-08 08:38:48 -04:00

Originally created by @lystopad on 5/27/2025

When setting the DEBIAN_FRONTEND environment variable, it's best to apply it directly to apt commands rather than setting it globally. If DEBIAN_FRONTEND=noninteractive is set as a persistent environment variable in the container image, it can affect other Debian-specific commands run after the container starts, potentially leading to unintended behavior.

Instead, consider using it like this:

DEBIAN_FRONTEND=noninteractive apt-get update
DEBIAN_FRONTEND=noninteractive apt-get install ...

This ensures the variable is only active during the apt operations and isn't retained in the final image, preventing any lingering side effects.

*Originally created by @lystopad on 5/27/2025* When setting the DEBIAN_FRONTEND environment variable, it's best to apply it directly to apt commands rather than setting it globally. If DEBIAN_FRONTEND=noninteractive is set as a persistent environment variable in the container image, it can affect other Debian-specific commands run after the container starts, potentially leading to unintended behavior. Instead, consider using it like this: DEBIAN_FRONTEND=noninteractive apt-get update DEBIAN_FRONTEND=noninteractive apt-get install ... This ensures the variable is only active during the apt operations and isn't retained in the final image, preventing any lingering side effects.

AtHeartEngineer closed this issue

2025-07-08 08:38:48 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#64