Pre-load Devbox environment in container entrypoints for LLM agents and CI/CD

オープン
  • 何か問題がありますか？
#2,797 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
go
領域
cli, devtools, infrastructure

調査の方向性

The issue does not identify implementation files or tests. Start by reading the existing devbox shell, devbox run, and container entrypoint code to understand how the environment is constructed and applied. The requested alternatives span CLI behavior, container startup, and environment export; done means a chosen approach reliably makes the Devbox environment available to non-interactive processes.

索引モデルが issue の本文から書いたものです。

説明

feature p3 processed triage
What problem are you trying to solve?

I want to run automated scripts or agents inside a Devbox-managed container where dependencies installed via devbox.json are immediately available in PATH—without requiring an interactive devbox shell session.
Currently, when launching a container (e.g., via devbox run or Docker), the environment variables and PATH modifications from Devbox are not applied unless the process runs inside an interactive Devbox shell. This breaks headless/automated workflows like CI jobs, LLM agents, or background services that need project-specific tools (e.g., go, python, node, custom binaries) available at startup.
Specifically, I'm building agentbox, where an LLM agent runs inside a container and needs immediate access to the project's toolchain to execute, test, or debug code. Having to manually enter devbox shell first defeats the purpose of an autonomous, reproducible environment.

What solution would you like?

Add support for non-interactive environment activation in Devbox containers. Specifically:

  1. devbox shell -c "<command>" (similar to bash -c) or similar flag that executes a command with the full Devbox environment (PATH, env vars, etc.). This is differs from commands from "devbox run" because thery are not defined in the devbox.json file.
  2. Container entrypoint option: Allow specifying a command in devbox.json or via CLI that runs automatically with the environment pre-loaded when the container starts (e.g., devbox container run --entrypoint "my-agent").
  3. Exportable environment script: Generate a shell script (e.g., devbox export-env) that can be sourced in a Dockerfile or entrypoint to initialize the environment for any subsequent command.

This would enable headless automation while preserving Devbox's reproducible dependency management—no need to bake custom images or manually manage PATH.

Alternatives you've considered
  • Manual eval "$(devbox shellenv)" in entrypoint: This works in some cases but adds complexity, requires bash/shell, and isn't officially documented for container use. It also doesn't handle all edge cases (e.g., non-shell processes).
  • Custom Docker images per project: Defeats the purpose of Devbox's dynamic environment management and increases build/maintenance overhead.
  • Wrapper scripts that invoke a command inside something like devox run -- bash or devbox shell -c "command": Limited by the fact that devbox shell is designed for interactive use; non-interactive usage is unreliable or unsupported.
主要言語
Go
スター
12.4k
フォーク
358
平均マージ
17時間 12分
マージ済み PR（30日）
31

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

jetify-com/devbox のほかの issue

jetify-com/devbox の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。