Skip to content

Injecting environment variables via Command? #85

@eropple

Description

@eropple

Hey there! I've started poking at birdcage for an open-source project I'm working on, and it's really cool. One thing that I'm running into that it doesn't do, however, is allow environment variables to be passed with the command--instead allowing either passing them by-name or passing the entire set of environment variables. For $reasons, I might need to gin one up and pass it directly to a command in my sandbox.

Before I go hacking away, I wanted to reach out and ask if there's a reason why Birdcage doesn't do this already? I am not super familiar with seccomp or seatbelt, so I didn't want to go dive down a rabbit hole if there's a technical reason it doesn't support that.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions