Jump to content

NodeLink Docker Containers Available on Dockerhub


Scyto

Recommended Posts

With the release of v10 i have updated my NodeLink docker containers.

The tag supports Linux (amd64, ARMv7 and ARMv8) and Windows (amd64).

For Linux:	docker run --name=NodeLink -v $PWD$:/NodeLink -v /etc/localtime:/etc/localtime:rw -p 8090:8090 scyto/nodelink
For Windows:	docker run --name=NodeLink -v $PWD$:C:\NodeLink -v /etc/localtime:/etc/localtime:rw -p 8090:8090 scyto/nodelink

Where $PWD$ is the path to where you want files on the host, this will allow you to reuse the files you have or bootstrap the creation of new ones

for more details see https://hub.docker.com/r/scyto/nodelink

Link to comment
Share on other sites

  • 8 months later...

This looks like a great idea to me as I'm trying to retire my old raspberry pi that is now only running a very old version of nodelink.

I tried to install, but I can't seem to get it to work.  Trying to install on ubuntu 18.  I made a nodelink folder and in place of the $PWD$ I have /usr/share/nodelink.

I'm not well versed in linux or docker so I'm likely missing something simple.

After it was made I looked at the container with portainer and the logs say:

2020-07-19T17:03:11.034681729Z checking if NodeLink exists

2020-07-19T17:03:11.043682891Z --2020-07-19 10:03:11-- http://automationshack.com/Files/NodeLink.dll

2020-07-19T17:03:11.107667799Z Resolving automationshack.com (automationshack.com)... 68.65.120.219

2020-07-19T17:03:11.185291462Z Connecting to automationshack.com (automationshack.com)|68.65.120.219|:80... connected.

2020-07-19T17:03:11.275521895Z HTTP request sent, awaiting response... 200 OK

2020-07-19T17:03:11.275555688Z Length: 632320 (618K) [application/x-msdownload]

2020-07-19T17:03:11.275562962Z Saving to: ‘/NodeLink/NodeLink.dll’

2020-07-19T17:03:11.275613877Z

2020-07-19T17:03:11.510217999Z 0K .......... .......... .......... .......... .......... 8% 295K 2s

2020-07-19T17:03:11.599020602Z 50K .......... .......... .......... .......... .......... 16% 325K 2s

2020-07-19T17:03:11.744566332Z 100K .......... .......... .......... .......... .......... 24% 343K 1s

2020-07-19T17:03:11.822284002Z 150K .......... .......... .......... .......... .......... 32% 647K 1s

2020-07-19T17:03:11.915259575Z 200K .......... .......... .......... .......... .......... 40% 606K 1s

2020-07-19T17:03:11.981893345Z 250K .......... .......... .......... .......... .......... 48% 646K 1s

2020-07-19T17:03:12.058600758Z 300K .......... .......... .......... .......... .......... 56% 654K 1s

2020-07-19T17:03:12.079640403Z 350K .......... .......... .......... .......... .......... 64% 2.31M 0s

2020-07-19T17:03:12.152468236Z 400K .......... .......... .......... .......... .......... 72% 687K 0s

2020-07-19T17:03:12.225882460Z 450K .......... .......... .......... .......... .......... 80% 680K 0s

2020-07-19T17:03:12.277675528Z 500K .......... .......... .......... .......... .......... 89% 966K 0s

2020-07-19T17:03:12.303464756Z 550K .......... .......... .......... .......... .......... 97% 1.88M 0s

2020-07-19T17:03:12.303655804Z 600K .......... ....... 100% 84.4M=1.0s

2020-07-19T17:03:12.303669470Z

2020-07-19T17:03:12.303765169Z 2020-07-19 10:03:12 (601 KB/s) - ‘/NodeLink/NodeLink.dll’ saved [632320/632320]

2020-07-19T17:03:12.303776140Z

2020-07-19T17:03:12.309449237Z --2020-07-19 10:03:12-- http://automationshack.com/Files/NodeLink.runtimeconfig.json

2020-07-19T17:03:12.361280055Z Resolving automationshack.com (automationshack.com)... 68.65.120.219

2020-07-19T17:03:12.439156994Z Connecting to automationshack.com (automationshack.com)|68.65.120.219|:80... connected.

2020-07-19T17:03:12.529202609Z HTTP request sent, awaiting response... 200 OK

2020-07-19T17:03:12.529242103Z Length: 154 [application/json]

2020-07-19T17:03:12.529251290Z Saving to: ‘/NodeLink/NodeLink.runtimeconfig.json’

2020-07-19T17:03:12.529276668Z

2020-07-19T17:03:12.529342682Z 0K 100% 16.6M=0s

2020-07-19T17:03:12.529374492Z

2020-07-19T17:03:12.529444383Z 2020-07-19 10:03:12 (16.6 MB/s) - ‘/NodeLink/NodeLink.runtimeconfig.json’ saved [154/154]

2020-07-19T17:03:12.529471894Z

2020-07-19T17:03:12.530493321Z starting NodeLink

This makes it look like it is running, but it dies right away and portainer status says stopped with exit code 0.

 

Anyone have any tips for getting this running?

 

Thanks

Link to comment
Share on other sites

  • 2 months later...

@danbutter the container works, i am using it, i am not sure what you are doing or what the issue is

You did map the the docker directory right with r/w perms so this is stateful?

So on first boot the container looks to see if it has nodelink, if it doesn't it downloads it.  I don't know why that causes an exit on your machine, it shouldn't.   On the next boot it will be like this in the logs (this is how i know your state is being thrown away). 

I suggest you use the docker run command and test that rather than use portainer, once you have it working as per my instructions then i suggest you migrate into portainer.

Also if you want help that's what the github is for - file an issue there and I will respond much faster.

date	stream	content
2020-09-25 06:16:12	stdout	2020-09-24 23:16:12 - GEM: No valid parameters setup for connection [gem1]
2020-09-25 06:16:12	stdout	2020-09-24 23:16:12 - Warning: Node definitions need updating in ISY, see NodeLink's Devices page
2020-09-25 06:16:08	stdout	2020-09-24 23:16:08 - ISY Node Server config detected (profile 2)
2020-09-25 06:16:08	stdout	2020-09-24 23:16:08 - ISY resolved to 192.168.1.97 (5.2.0)
2020-09-25 06:16:08	stdout	2020-09-24 23:16:08 - Web config server started (http://172.17.0.4:8090)
2020-09-25 06:16:08	stdout	2020-09-24 23:16:08 - Net Core Version: 3.0.0
2020-09-25 06:16:08	stdout	2020-09-24 23:16:08 - OS: Linux scyto-nodelink1 4.4.180+ #40850 SMP Wed Sep 2 17:03:14 CST 2020 x86_64 GNU/Linux
2020-09-25 06:16:08	stdout	root@scyto-nodelink1:/# 2020-09-24 23:16:08 - ISY NodeLink Server v0.10.6 started
2020-09-25 06:16:06	stdout	starting NodeLink
2020-09-25 06:16:06	stdout	checking if NodeLink exists

 

 

 

Link to comment
Share on other sites

  • 4 months later...

I was trying again to get this running and ran into this:

checking if NodeLink exists
starting NodeLink
It was not possible to find any compatible framework version
The specified framework 'Microsoft.NETCore.App', version '5.0.0' was not found.
  - The following frameworks were found:
      3.0.0 at [/usr/share/dotnet/shared/Microsoft.NETCore.App]

You can resolve the problem by installing the specified framework and/or SDK.

The .NET Core frameworks can be found at:
  - https://aka.ms/dotnet-download

Wondering if there are any plans to update the container.

I'll post this on the github also to get your attention quicker.

 

Thanks

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...