GNOME Builder does not propagate `environment.d` environment into podman containers
Personally, instead of going through shell as commonly done, I set up environment using environment.d
, including my PATH
or overrides for paths for eg. rustup or cargo not to clutter my home directory root and instead of put stuff at XDG_DATA_HOME
. This has benefits as it's shell-portable on basically all systemd systems and the environment variables gets registered even when shell is not involved session startup, which is a case (AFAIK) in GNOME Shell Wayland session.
This hit me when, as on Fedora Silverblue, used my Distrobox Podman container where I have stuff like linker, but also other dev libs installed. As my PATH
config was not applied, it couldn't find cargo
. Of course I can go edit .buildconfig
for doing environment variable overrides, but that does not support variable substitutions, so I can't just prepend to my PATH
so this solution is not sustainable.
I understand when building in containerised environment, you probably do not want your environment variables to affect the build, but distroboxes / toolboxes / … are it's own way of using OCI container tech, so maybe, add option to propagate (certain) environment variables?
I was not exactly how exactly is this of buggy behaviour or just a missing or even intended feature and chose to write here.
Thanks ^^