better test + migration
This commit is contained in:
1 parent
27b713affa
commit
ab8260a5d0
8 files changed
+202
-34
No files matched your search
@@ -827,6 +827,41 @@ sudo tar -C /path/to/HERMES_HOME/.hermes -cf - . \
|
||||
| hermenix vm ssh 'mkdir -p /var/lib/hermes/.hermes-old && tar -C /var/lib/hermes/.hermes-old -xf -'
|
||||
```
|
||||
|
||||
### `hermes setup` fails with "docker not found on PATH. Cannot route to container"
|
||||
|
||||
`hermenix migrate` automatically excludes `.local/bin` and `.hermes-installed`
|
||||
from the migration tar, so this should not happen with current versions.
|
||||
If you see it after a migration with an older build, the source's
|
||||
`.local/bin/hermes` (a Docker-routing launcher from the previous environment)
|
||||
was copied into the guest and is shadowing the native install.
|
||||
|
||||
Fix inside the guest:
|
||||
|
||||
```bash
|
||||
# Remove the stale launcher
|
||||
rm -f ~/.local/bin/hermes
|
||||
|
||||
# Reinstall the native hermes binary
|
||||
curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh \
|
||||
| bash -s -- --non-interactive --skip-setup
|
||||
|
||||
# Verify it's a real binary, not a shell script
|
||||
file ~/.local/bin/hermes
|
||||
|
||||
# Now proceed with setup
|
||||
hermes setup
|
||||
```
|
||||
|
||||
If `hermes-install.service` never ran because `.hermes-installed` was also
|
||||
migrated from the source, you may instead let systemd do it:
|
||||
|
||||
```bash
|
||||
rm -f ~/.local/bin/hermes ~/.hermes-installed
|
||||
sudo systemctl start hermes-install
|
||||
journalctl -fu hermes-install # watch until complete
|
||||
hermes setup
|
||||
```
|
||||
|
||||
|
||||
## Hacking on this repo
|
||||
|
||||
|
||||
Reference in new issue
Block a user