Cairn
NousResearch/hermes-agent

docker_env config not passed to containers

Cluster 16214 · environments. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These issues and PRs concern a bug where terminal.docker_env values from config.yaml are not forwarded to spawned containers, and fixes to propagate that configuration through file and terminal tool container creation.

Open issues1

  • Issue#16214terminal.docker_env from config.yaml never reaches the spawned container

Open PRs1

  • PR#90050test(tools): cover container config propagation across sandbox creation

2 PRs closed without merging

From the close comments: partial fix 1 · other 1

  • #16215 fix(docker-env): bridge `terminal.docker_env` from config.yaml to container · partial fix → 116a144, #16215, #22626, #16348, #17620, #8320
  • #16348 fix(file): pass docker_env to file tool containers · other
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
environments
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/16214.json
cluster/16214.md