Pre-load Devbox environment in container entrypoints for LLM agents and CI/CD
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 25/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- go
- Ambito
- cli, devtools, infrastructure
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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:
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.- 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").
- 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 -- bashordevbox shell -c "command": Limited by the fact that devbox shell is designed for interactive use; non-interactive usage is unreliable or unsupported.
- Lingua principale
- Go
- Stelle
- 12.4k
- Fork
- 358
- Merge medio
- 17h 12m
- PR unite (30g)
- 31
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di jetify-com/devbox
-
feature triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
jetify-com/devbox#3038 ·
I maintainer di solito rispondono entro 1 giorno
-
pulumi is outdatedApertabug p4 package processed triage unrelated
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
jetify-com/devbox#2898 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
p4 processed unrelated
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
jetify-com/devbox#2750 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
StorydenApertap4 package processed triage unrelated
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
jetify-com/devbox#2685 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
looks easy p4 package processed triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 60/100
jetify-com/devbox#2656 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di jetify-com/devbox
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
area/ambient
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
-
`autorelease-tag.yml` starts after any run named "💡Fingerprints Update"Forse già presa @Mzack9999 l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
projectdiscovery/wappalyzergo#184 ·
-
bug needs-triage P3 tier:2-standard
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
krakenhavoc/cmd_and_ctrl#4990 ·
I maintainer di solito rispondono entro 1 giorno