Skip to content

Conversation

@prekucki
Copy link
Member

@prekucki prekucki commented Jul 8, 2025

Summary

Fixes a critical bug where container environment variables (including PATH) were not being passed to executed processes in the guest VM.

Root Cause

The environment variable logic in runtime/init-container/src/init.c line 989 was accidentally inverted during code formatting between v0.4.2 and current version.

v0.4.2 (working):

new_proc_args->envp ?: environ

Before this fix (broken):

new_proc_args->envp ? NULL : environ

After this fix:

new_proc_args->envp ? new_proc_args->envp : environ

Impact

  • Container-specified environment variables (like PATH) are now properly preserved
  • Fixes regression where containers couldn't set custom environment variables
  • Ensures backwards compatibility with existing container images

Test plan

  • Build and test with containers that specify custom environment variables
  • Verify PATH is preserved for containers like Blender that depend on custom paths
  • Confirm fallback to system environment when no container env is specified

prekucki added 3 commits July 8, 2025 15:38
Fixed inverted logic in init.c line 989 that prevented container
environment variables (including PATH) from being passed to executed
processes. The bug was introduced when `?:` operator was incorrectly
changed to `? NULL :` during code formatting.

Before: new_proc_args->envp ? NULL : environ
After:  new_proc_args->envp ? new_proc_args->envp : environ

This ensures container-specified environment variables are properly
preserved in the guest VM.
- Update actions/checkout from v1/v2 to v4
- Update actions/cache from v1 to v4
- Update actions/github-script from v3.0/0.9.0 to v7

This resolves CI failures caused by deprecated action versions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants