#'docker run nousresearch/hermes-agent:latest hermes --tui' fails

1 messages · Page 1 of 1 (latest)

empty marsh
#

My use case: I don't want to run hermes on my main machine and I don't want long running hermes-agent containers.
Reasons: I'd like to use the latest hermes-agent image every time I spin up the agent for some development work.
Expectation: The tui version of hermes-agent runs without issue.
My main system: macbook

Current output:

$ docker run nousreserach/hermes-agent:latest ... hermes --tui
...
Done: 89 new, 0 updated, 0 unchanged. 89 total bundled.
Installing TUI dependencies…
npm install failed.
$ <-- kicks me back to my host terminal session
devout parrot
#

cc @spark turret

spark turret
#

Huh, that has been working for me, let me try it now

#

Oh wait

#

I think you're invoking it slightly incorrectly

#

I could also swear we pushed a fix for this exact issue a few days ago thonk

#

Dang, looks like the fix got undone. Thanks for calling this out, it's a bug. I'll try and have it fixed later today.

#

Short term workaround: use one of the slightly older pinned versions of the agent that doesn't have the issue

spark turret
#

Just merged in a fix, the next docker image built should contain it

empty marsh
#

I'm still seeing an 'npm install failed.' when pulling the latest image.

$ herm --tui
latest: Pulling from nousresearch/hermes-agent
9b556b651166: Pull complete
b42ec740b4c4: Pull complete
0bf95cc7b4f4: Pull complete
f0e3ef619b1a: Pull complete
05f0c9eb9a07: Pull complete
605de49646e4: Pull complete
7165e5a896a5: Pull complete
5b6546c96fa3: Pull complete
fb1979587dc9: Pull complete
4f4fb700ef54: Pull complete
ba15f5e1e294: Pull complete
595b4dbb127f: Pull complete
e98df2cbbe3a: Pull complete
86d071f2ab34: Pull complete
321e7df6d87a: Download complete
Digest: sha256:e28e3a34ba2b2871142f01ab20c63f5ef1e87578a7d023160f2e57dffc4ccd95
Status: Downloaded newer image for nousresearch/hermes-agent:latest
docker.io/nousresearch/hermes-agent:latest
usage: basename string [suffix]
       basename [-a] [-s suffix] string [...]
docker
run
-it
--name
-e
HOME=/workspace
-v
/Users/myusername/ai-projects/hermes-testing/.hermes:/opt/data
-v
/Users/myusername/ai-projects/hermes-testing:/workspace
-w
/workspace
nousresearch/hermes-agent:latest
hermes
--tui
Fixing ownership of /opt/data to hermes (10000)
Dropping root privileges
Syncing bundled skills into ~/.hermes/skills/ ...
  ↑ subagent-driven-development (updated)
  + spike
  + kanban-worker
  + kanban-orchestrator
  + pretext
  + sketch
  + comfyui
Done: 6 new, 1 updated, 82 unchanged. 89 total bundled.
Installing TUI dependencies…
npm install failed.
$ <--- kicks me back out to my host machine.
#

This isn't a really high priority item, since I can use the older cli interface, just wanted to call out that --tui won't work for fresh docker container spin ups. Most people are probably using a hermes container longer than myself, and would simply install the missing deps inside the contianer and continue on.

#

this is what myherm shell function is doing:

docker pull nousresearch/hermes-agent:latest
docker run -it --name "$(basename $(pwd))" -e HOME=/workspace -v "$(pwd)/.hermes:/opt/data" -v "$(pwd):/workspace" -w /workspace nousresearch/hermes-agent:latest hermes --tui
spark turret
#

:sigh: I'll have to look into what broke this time

devout parrot
#

@spark turret has this been resolved?

empty marsh
#

@devout parrot It seems resolved on my end. In a fresh directory I ran:

docker pull nousresearch/hermes-agent:latest

docker run -it --name "$(basename $(pwd))" -e HOME=/workspace -v "$(pwd)/.hermes:/opt/data" -v "$(pwd):/workspace" -w /workspace nousresearch/hermes-agent:latest hermes --tui

And I was greeted with an unconfigured, yet working tui enabled hermes agent.
I am no longer seeing the 'npm install failed' issue.

Thank you Nous team!