Moving to Docker

[akbooer]

OK, now I have a problem.

It was all going so well until I realised that all incoming IP addresses were being mapped to 172.17.0.1by the LuaSocket library.

Reading the Docker docs: https://docs.docker.com/config/containers/container-networking/

"By default, the container is assigned an IP address for every Docker network it connects to. The IP address is assigned from the pool assigned to the network, so the Docker daemon effectively acts as a DHCP server for each container. Each network also has a default subnet mask and gateway."

But I don't understand, yet, how this works if I want a straight-forward mapping of IPs from my LAN into the Docker container.

It may be that the Synology Docker interface is not adequate for this and I have to revert to the command line?

Any advice/clarification much appreciated.

[PerH]

ok, i got the IP stuff figured. A custom network must be made in order to choose IP, then connect the container.

sudo docker network create -d bridge --subnet=192.168.0.0/16 --ip-range=192.168.0.0/24 --gateway=192.168.0.254 <Network name>
sudo docker network connect --ip=<IP> <Network created by you> <container name>
sudo docker network disconnect bridge <container name>

Still struggling with getting openluup to work as i want it.. tried to copy the cmh-ludl folder from my prod. system to the _data folder for my volume, but can't seem to overwrite user_data.json..

Tried to bind to a folder instead, but then it won't start, as the folder is missing the "openLuup_reload_for_docker" file..

what do i do next?

[akbooer]

@perh said in Moving to Docker:

but can't seem to overwrite user_data.json.

You can't do this when the system is running, because it gets overwritten with the current system state on restarts. Stop openLuup with a /data_request?id=exit request, change the file, then stop and restart the container (to restart openLuup.)

[PerH]

offcourse.. its getting late! thanks.

[PerH]

My plan for USB devices was to have ser2net on host for all usb's, and then bind the dockers to the ser2net ports for the devices. If however ser2net is sending on ie. port 3485, the docker can't bind to that port.

How can I do this?

[PerH]

Solution: Don't bind the port at all in the docker, and call the IP of the host in the application running inside container..

EDIT: Or even better, use the "gateway" IP in the internal docker network, this way its easier to move the whole setup to hardware with a different IP address without editing this attribute.

[LibraSun]

For funsies, I decided to hop on board with OpenLuup by running @vwout 's pre-built container (excellent piece of work, by the way, sir!) on my Synology NAS using Docker's wizards.

It took some convincing by others more experienced than myself (both with OpenLuup and Docker), NOT to change anything in the Synology NAS GUI before simply LAUNCH-ing the Image. The only thing I set manually were the ports - changing from 'Auto' to numbers matching those in the right column under Advanced Settings > Ports, then clicking "Apply".

From within DiskStation on your Synology NAS:

1. Open Docker (install from Package Center if not installed)
2. Registry > search for "OpenLuup" > select 'vwout / openluup' (alpine)
3. Click Download.
4. Images > select 'vwout / openluup' > click Launch.
5. On Advanced Settings tab > 'Advanced Settings' > check 'Enable auto-restart'
6. On Ports tab:
   • Change each port from "Auto" to match right-hand #.
7. On Environment tab:
   • Change (if desired) the 'Value' field next to TZ, from 'UTC' to your time zone (e.g. GMT-5)
8. Click Apply

Your new OpenLuup container will now start.

Head over to http://<nas_ip>:3480/console for some fun with OpenLuup!

BONUS: For step-by-step instructions on linking your Vera(s) to OpenLuup, see this reply below.

THANKS!

[akbooer]

My first foray into Docker was with this image, on Synology NAS, but I didn’t mount external volumes. It’s worked flawlessly, which is just as well because I know very little about Docker, although I’m learning a bit because I’m creating my own version from a raw Alpine base.

So I’ve not seen this issue, ever... which doesn’t really help you at all, except to know that it can work.

[toggledbits]

On the NAS, open Docker, then click on the container in the Container list, then click the Details button. A dialog will pop up which has a "Log" tab, and there you will find the console output of the container, which could have some messages related to the stop that will help you troubleshoot.

[kfxo]

I think I had this same issue. If you copy the files in cmh-ludl from an existing openluup install into ' /OpenLuup/openluup-env' it should start right up.

[LibraSun]

I checked the log per your advice and saw the following line repeated 42 times:

/bin/sh: can't open '/etc/cmh-ludl/openLuup_reload_for_docker': No such file or directory

The other piece of advice about copying existing openLuup files makes sense, although I have never used openLuup before so would not know where to begin.

Is this the classic chicken and the egg problem?

[kfxo]

There is a post from me above in this thread (sorry don't know how to link specific post) that explains how I got it to work. Have you tried that? I think the issue is synology gui does not support the correct type of volumes and you have to ssh into synology and run the correct docker command to set it up.

[LibraSun]

@kfxo said in Moving to Docker:

you have to ssh into synology and run the correct docker command to set it up.

That's exactly what I was being lazy about and hoping to avoid altogether, but now it appears necessary and I will delve into that ASAP.

Thanks for the suggestion! I will also amend my step-by-step tutorial once I get mine working so that others can avoid the pitfalls I encountered.

[LibraSun]

UPDATE (if anyone is still playing along...):
Again for fun, I tried LAUNCH-ing the vwout/openluup Image directly, without modifying ANY settings in the Synology NAS Docker GUI, and ... lo and behold IT WORKS. That is, the Container runs without errors, the log appears robust and correct, and it even shuts down gracefully as advertised.

Both the port:3480 and :3480/console are now up and accessible. YAY!

I've clearly taken a step in the right direction, thanks to y'all's input. I'll go update my HOW-TO post, above, now.

[akbooer]

OK, that sounds like what I did...

@akbooer said in Moving to Docker:

but I didn’t mount external volumes

[LibraSun]

@akbooer I'm noticing two things in my OpenLuup system:
(a) there's a minor typo "Unistall" over the right column of Plug-Ins page
(b) mine shows "not.installed" for VeraBridge, yet the .lua file for it is present

How shall I go about setting up VeraBridge? The docs mention clicking "UPGRADE" but that portion of the page is blank.

[akbooer]

@librasun said in Moving to Docker:

(a) there's a minor type "Unistall" over the right column of Plug-Ins page

So there is! Well spotted.

@librasun said in Moving to Docker:

(b) mine shows "not.installed" for VeraBridge, yet the .lua file for it is present

Yes, it's a bit of a hangover form the past. VeraBridge is now a standard part of the openLuup installation – looks like I need to update the docs.

@librasun said in Moving to Docker:

How shall I go about setting up VeraBridge? The docs mention clicking "UPGRADE" but that portion of the page is blank.

Yes, that is blank, now (although not so on the AltUI equivalent page.) The corrrect way is:

• go to the openLuup console Tables > Devices Table page
• press the %(#008e00)[Create] button
• fill in the menu with your device name (eg. Vera)
• start typing D_VeraBridge.xml in the next box (it has autocompletion)
• ditto I_VeraBridge.xml
• click the %(#ff2600)[Create Device] button
• click %(#4e8f00)[Go to new device page] button
• go to the attributes tab and fill in the IP address of your Vera
• select Reload Luup Engine from the Utilities menu

This could be easier, but its the standard way for all new plugins (aside from those installed from the Alt App Store.)

Sorry.

[LibraSun]

Excellent, and somewhat of a relief to know I could not possibly have figured this out on my own.
THANK YOU!

[akbooer]

@akbooer said in Moving to Docker:

It was all going so well until I realised that all incoming IP addresses were being mapped to 172.17.0.1by the LuaSocket library.

For anyone who may remotely be interested, I stumbled across the reason for this whilst playing with a raw Alpine docker... it's because the default is to use the Docker network bridge which restricts access to a few specified ports. The alternative is to open it up to the whole local network using the host setting, in which case the expected IP addresses are discovered by openLuup.

[Crille]

@akbooer and @LibraSun I think mine had an update button in AltUi and I just pressed it. After that VeraBridge showed up as a device and I configured it.