Jump to content
XPEnology Community

venturis

Transition Member
  • Posts

    8
  • Joined

  • Last visited

venturis's Achievements

Newbie

Newbie (1/7)

0

Reputation

  1. Thanks for the instructions. I did something very similar from instructions I found on the internet. I created the key and registered the key in the appropriate file on the ESXi host and confirmed. When I try starting the pi-control container this time I get the following generated in the log: Warning: Permanently added '192.168.0.200' (RSA) to the list of known hosts. Permission denied (publickey,keyboard-interactive). If the key I created was properly registered on the ESXi host I should be able to SSH to the ESXi host from the Xpenology DSM teminal without the password but I always get the password prompt. I found this article which seems to indicate that I might need to make some more changes to the ESXi host https://kb.vmware.com/selfservice/micro ... Id=1002866
  2. I'm close to throwing in the towel here. I have to admit I'm a complete novice at Linux and Docker and I've only made the progress I've made with information in the posts above. I have both containers running and can access the SmartX web page but I don't believe I've properly set up the encryption key that allows pi-control to access the ESXi host without password authentication. The SmartX web page simply displays "updating". Looking at the SmartX container log shows repeated errors every 15 seconds stating "connection refused while connecting to upstream client...." I found some information on creating a public key but not sure were to put the key to make it accessible to the pi-control container. If anyone can help with step-by-step instruction for setting up the pi-control to ESXi host authentication it would be much appreciated.
  3. Any updates on the x64 Linux image for SmartX? I tried the published version on my Xpenology v5644.5 running under ESXi 5.5 but it bombs out when starting the container.
  4. I tried the command line and get a "repository not found" fatal error. Reading through the bug report at the link provided seems to be a different issue than having here. I can find the repository with the Docker GUI but it fails to download. Command line pull also fails. Will wait until Djey has recreated the repository and will try again.
  5. I keep getting an "operation failed" error message when trying to add the Pi-control image to docker using the GUI. I've not tried the command line. I pulled down the first two images again as a test and they pulled down without error. UPDATE: I just tried to pull the pi-control-linux-x64 image using the command line....I get a "repository not found" error.
  6. That's terrific.....I'll give it a try today. Thanks.
  7. Thanks. I thought that the containers were created to run on Docker in an Xpenology VM on ESXi. Ill keep a look out for the x64 version.
  8. Hi, I thought I would give the Docker containers a go myself but found I was getting the following error when I tried running the docker container for Pi-control "System Error: exec format error" I'm new to Docker but have followed the instructions in the Wiki and put all my ESXi config into the command string correctly. Any ideas? I've tried several times without success. Im running ESXi 5.5 on a Microserver G8 with an XPENOLOGY 5.2 virtual machine with RDM drives.
×
×
  • Create New...