Allow providing custom --env variables to be used in the container#171
Merged
euanh merged 1 commit intoapple:mainfrom Feb 2, 2026
Merged
Allow providing custom --env variables to be used in the container#171euanh merged 1 commit intoapple:mainfrom
--env variables to be used in the container#171euanh merged 1 commit intoapple:mainfrom
Conversation
This is needed for swift-backtrace. # Conflicts: # Sources/containertool/containertool.swift
euanh
added
kind/enhancement
euanh
approved these changes
Feb 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is needed for swift-backtrace #154 . Following PR should be able to address that once we figure out https://forums.swift.org/t/where-to-source-swift-backtrace-binaries/84499
Motivation
#154 ability to see backtraces for swift binaries. But generally it's also useful to set environment variables in containers for certain use cases.
Modifications
Allow passing in
--env, so you can directSWIFT_BACKTRACE.Result
Swift backtrace is possible on the end-user side. Example: wendylabsinc/wendy-agent#290
Test Plan
I did manual testing already in wendy-agent. You can trivially test this by passing
--envand reading it out in a swift app with the following code: