NousResearch/hermes-agent

Docker network flag duplication causing container start failure

Cluster 100248. Data as of 2026-10-24 04:06 UTC

Nothing open on GitHub. Fix merged in #103644 on 5 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #103644. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #103644. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #103644, then check it covers your case.

Read #103644 Pick up a Lab task

These issues and PRs address a bug where setting docker_network: false alongside a --network flag in docker_extra_args causes the --network flag to be emitted twice, resulting in every container failing to start with exit code 125. The fixes aim to skip the implicit --network=none when a network is already specified in extra args.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#103644 fix(docker): docker_network: false plus a --network flag in docker_extra_args no longer makes every container start fail (#100248, salvage #100256)

merged to main

files: contributors/emails/[redacted:email], tests/tools/test_docker_network_config.py, tools/environments/docker.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

#100256 fix(tools): reconcile docker_network with --network in docker_extra_args · done elsewhere → d72cbbc, #103644
#100266 fix(docker): skip implicit --network=none when extra args set a network · superseded by another PR → #100256

Closed issues · 1

Closed#100248[Bug]: docker_network: false plus any --network in docker_extra_args emits the flag twice — every container start fails with exit 125

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

Merged PRs: #103644
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 5 Sep 2026

For your agent

The same facts, typed.

cluster/100248.json
cluster/100248.md