-
Notifications
You must be signed in to change notification settings - Fork 5
Description
Describe the bug
When running hyperdrive stakewise wallet generate-keys, Hyperdrive successfully generates the validator key(s) but fails at the final step where it tries to restart the Validator Client container. The command prints a Docker API version error and instructs the user to restart the VC manually.
To Reproduce
Steps to reproduce the behavior:
-
Run:
hyperdrive stakewise wallet generate-keys
-
Choose 1 (or any number) when prompted.
-
Wait until key generation completes.
-
Observe the restart failure at the end:
Restarting Validator Client to load the new keys... error WARNING: error restarting validator client: error during Service RestartContainer request: Error response from daemon: client version 1.40 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version Please restart your Validator Client in order to attest with your new keys!
Expected behavior
After generating keys, Hyperdrive should restart the Validator Client automatically so it loads the new keystores, without requiring manual intervention.
Screenshots
N/A (can provide terminal output screenshots if needed)
Environment Info:
- OS + version: Arch Linux x86_64, kernel 6.17.9-arch1-1 (Host: NucBox G3, Intel N100)
- Beacon client: Lighthouse v8.0.1
- Execution client: Nethermind v1.35.3
- Hyperdrive: 1.3.0
- StakeWise module image: nodeset/hyperdrive-stakewise:v1.3.0
- Docker version: 29.1.3, build f52814d454
Additional context
Key generation succeeds and the new key is present in the keystore list, but the automatic restart step fails.
Manual workaround works immediately:
docker restart hyperdrive_sw_vcAfter restarting, Lighthouse VC logs show the new pubkey is enabled and validators are initialized normally.
The error suggests Hyperdrive (or a dependency used to control Docker) is using an outdated Docker API client (1.40), even though the host Docker Engine is up to date.