So I am trying to get NodeLink to work in a QNAP Docker image. My first attempt I got everything running but then when the NodeLink container was restarted the configuration would be lost. IOGuy told me I needed to save NodeLink files outside the container and it took me a while but I figured out (*I think*) how to do that as I see the files now in the folder. Whew. 

Now the issue is when I restart and go into the NodeLink configuration but its getting an ISY timeout error. See below:

2018-03-03 07:22:00 - ISY NodeLink Server v0.9.10 started
2018-03-03 07:22:00 - Mono version: 5.8.0.127 (tarball Wed Feb 21 16:54:42 UTC 2018)
2018-03-03 07:22:00 - ISY resolved to 192.168.0.81
2018-03-03 07:22:00 - ISY: Node Server request sent
2018-03-03 07:22:00 - Web config server started (http://192.168.0.132:8090)
2018-03-03 07:22:04 - ISY Error: No route to host (profiles/ns/0/connection)
2018-03-03 07:22:04 - ISY Error: Error getting Node Server list - Root element is missing.
2018-03-03 07:22:04 - Unable to determine ISY Node Server profile number
2018-03-03 07:22:06 - Web Request: /index.htm
2018-03-03 07:22:08 - Web Request: /general.css
2018-03-03 07:23:19 - ISY Error: Timeout from the ISY (nodes)

Help!?  I tried to use "PING" to see if I could ping FROM the container to the ISY IP but PING is not installed and I dont know the proper command to install it. I an ping the container and connect to the NodeLink docker container from another PC.

After I get this setup I plan on making a step by step for other docker noobs like me with purdy pictures. lol

I suggest you use a QNAP LXC Container.  It allows you to add additional packages and store setting within the image like a VM, but without the overhead of a VM

https://www.qnap.com/solution/container_station/en-us/

I've given away all my RPis since using LXC Containers.  

 

 

 

 

Edited March 3, 20187 yr by elvisimprsntr

I suggest you use a QNAP LXC Container.  It allows you to add additional packages and store setting within the image like a VM, but without the overhead of a VM
https://www.qnap.com/solution/container_station/en-us/
I've given away all my RPis since using LXC Containers.  
 
 
 
 

Thanks. I am such a noob ☹️ Do you suggest Debian or Ubuntu?

13 minutes ago, Scottmichaelj said:

 

Thanks. I am such a noob ☹️ Do you suggest Debian or Ubuntu?

 

I am sure either will work, but most guides seem to be Ubuntu based, which is what I use.  

Debian is the base for Ubuntu (and many other distros).  I would stick with it.  

Personally I'd stick with docker, it's a lighter footprint with less to maintain.  

Your error is a network issue.  Find a solution in the QNAP forums and move on.  

Debian is the base for Ubuntu (and many other distros).  I would stick with it.  
Personally I'd stick with docker, it's a lighter footprint with less to maintain.  
Your error is a network issue.  Find a solution in the QNAP forums and move on.  

Thanks. I spent time digging last night but the only way to confirm I can’t connect to the ISY is PING. Which is weird bc I can connect to the NodeLink setup page fine, the Docker went to the internet and grabbed the NL update fine. Wouldn’t that mean I could connect to the local IP? So why is it having an issue finding the ISY? [emoji36] Argh!

I suggest you use a QNAP LXC Container.  It allows you to add additional packages and store setting within the image like a VM, but without the overhead of a VM
https://www.qnap.com/solution/container_station/en-us/
I've given away all my RPis since using LXC Containers.  
 
 
 
 

one unintended consequence you might consider is that it might shorten your hdd life of you sleep your hdd"s! thus the tco might be higher than running an RPi3? i use a Synology NAS and I've backed away from a couple of apps for this very reason! if your hdd's are always spinning they use a lot more power and generate a lot of heat too. hdd killers...

Sent from my SM-N910W8 using Tapatalk

3 hours ago, johnstonf said:

one unintended consequence you might consider is that it might shorten your hdd life of you sleep your hdd"s! thus the tco might be higher than running an RPi3? i use a Synology NAS and I've backed away from a couple of apps for this very reason! if your hdd's are always spinning they use a lot more power and generate a lot of heat too. hdd killers...

Sent from my SM-N910W8 using Tapatalk
 

A NAS with sufficient RAM, a lightweight container (Docker or LXC) which does have have heavy disk usage will not tax the drives.  This is why one uses NAS class drives which are designed for exactly this type of application, and ensure there is adequate ventilation.  I read somewhere that constant stop/start of the drives and thermal cycling contribute to more premature failures.  

So...

2 hours ago, elvisimprsntr said:

A NAS with sufficient RAM, a lightweight container (Docker or LXC) which does have have heavy disk usage will not tax the drives.  This is why one uses NAS class drives which are designed for exactly this type of application, and ensure there is adequate ventilation.  I read somewhere that constant stop/start of the drives and thermal cycling contribute to more premature failures.  
So...

different strokes for different folks... my 6 NAS  RAID5 drive's sleep 80-90% of the time, and Raspberry Pi uses very little power, so i love offloading tasks to one of these tiny guys. just something to keep in mind...

Sent from my SM-N910W8 using Tapatalk
 

Edited March 12, 20187 yr by johnstonf