Issues while restoring stolon wal-e

below are the steps performed:
1. Performed backup
stolonctl update --patch ‘{ “pgParameters” : { “archive_mode”: “on”, “archive_command”: “envdir /etc/wal-e.d/env wal-e wal-push %p” } }’ --cluster-name=rc-cluster --store-backend=etcdv3 --store-endpoints=

2. restore
stolonctl init ‘{“synchronousReplication”: false, “usePgrewind”: true, “initMode”: “pitr”, “pitrConfig”: { “dataRestoreCommand”: “envdir /etc/wal-e.d/env wal-e backup-fetch %d LATEST” , “archiveRecoverySettings”: { “restoreCommand”: “envdir /etc/wal-e.d/env wal-e wal-fetch “%f” “%p”” } } }’ --cluster-name=rc-cluster1 --store-backend=etcdv3 --store-endpoints=
Sentinel Logs:
cmd/sentinel.go:924 waiting for db to converge {“db”: “f411f39e”, “keeper”: “keeper0”}

Keeper Logs:

2020-10-16T10:53:14.759Z INFO cmd/keeper.go:1171 restoring the database cluster
2020-10-16T10:53:14.774Z INFO cmd/keeper.go:1196 executing DataRestoreCommand
/bin/sh: 1: envdir: not found
2020-10-16T10:53:14.775Z ERROR cmd/keeper.go:1198 failed to restore postgres database cluster {“error”: “error: exit status 127”}
2020-10-16T10:53:19.777Z ERROR cmd/keeper.go:1063 db failed to initialize or resync
2020-10-16T10:53:19.781Z INFO cmd/keeper.go:1094 current db UID different than cluster data db UID {“db”: “”, “cdDB”: “f411f39e”}

@sgotti Can you please reply , this is what is mentioned in Stolon documentation and delay in reply causes the issues to persist.