I'm trying to set up your cluster concept for Autonomy but I keep getting an error and I've not been able to find out what is causing it. I've set up the two containers "nats" and node" but cannot get the node to run without error. Not sure where the error is coming but this is in the node error log (don't see subspace node actually running). I'd have previously run the node as a cli node and it still runs fine. I've tried my own setup with names and ip address and I've also gone back and duplicated your setup exactly. Here are some of the errors repeated over and over,
Error: SubstrateService(Other("Failed to convert network keypair: Os { code: 13, kind: PermissionDenied, message: \"Permission denied\" }"))
Error: SubstrateService(Other("Failed to convert network keypair: Os { code: 13, kind: PermissionDenied, message: \"Permission denied\" }"))
Thought it ran as root so don't why where there should be a permission issue. Error 13 is an unable to mount but the node data is on /home/subspace which is always mounted and the actual error is a key pair error. It appears that the node starts over and over so I guess the error is coming from the node starting up. Starts up find with my cli setup. I'm still looking but if you have seen this before or any suggestions, I would appreciate them.
For the Node I typically use a volume that is created when the container is deployed. It sounds like maybe you are using a folder on your system which means you likely need to set the ownership to nobody:nogroup for just that folder. Something like `sudo chown -R nobody:nogroup /home/subspace` and running your container.
Thanks Alex. Yes I am just using a folder under my home directory for node data. Currently owned by subspace. I’ll try your suggestion. I also am running spacemesh in Portainer fine but not as cluster. Thanks again.
Alex,
I'm trying to set up your cluster concept for Autonomy but I keep getting an error and I've not been able to find out what is causing it. I've set up the two containers "nats" and node" but cannot get the node to run without error. Not sure where the error is coming but this is in the node error log (don't see subspace node actually running). I'd have previously run the node as a cli node and it still runs fine. I've tried my own setup with names and ip address and I've also gone back and duplicated your setup exactly. Here are some of the errors repeated over and over,
Error: SubstrateService(Other("Failed to convert network keypair: Os { code: 13, kind: PermissionDenied, message: \"Permission denied\" }"))
Error: SubstrateService(Other("Failed to convert network keypair: Os { code: 13, kind: PermissionDenied, message: \"Permission denied\" }"))
Thought it ran as root so don't why where there should be a permission issue. Error 13 is an unable to mount but the node data is on /home/subspace which is always mounted and the actual error is a key pair error. It appears that the node starts over and over so I guess the error is coming from the node starting up. Starts up find with my cli setup. I'm still looking but if you have seen this before or any suggestions, I would appreciate them.
Thanks
For the Node I typically use a volume that is created when the container is deployed. It sounds like maybe you are using a folder on your system which means you likely need to set the ownership to nobody:nogroup for just that folder. Something like `sudo chown -R nobody:nogroup /home/subspace` and running your container.
Thanks Alex. Yes I am just using a folder under my home directory for node data. Currently owned by subspace. I’ll try your suggestion. I also am running spacemesh in Portainer fine but not as cluster. Thanks again.