Moving to Docker

[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.

[akbooer]

@crille

Yes, thanks indeed for pointing that out. It certainly works...

...my only reason for showing the longer workflow was that @LibraSun appeared to has been looking at the openLuup console page where there is no such button for VeraBridge.

As a plus, it also made @LibraSun feel good about not being able to guess how to do it!

[parkerc]

@librasun said in Moving to Docker:

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?

I decided to have a go installing the Docker openLuup (via my QNAP ContainerStation) - but I’m getting the same error.

Now, in my Docker compose I’ve mapped folders/volumes to the host machine, and that mapping looks to be working as the install creates the desired folders, my issue seems like it’s possibly straightforward, in that when it fires up, it’s looking for something called openLuup_reload_for_docker and it’s not there (as all the folders it created are empty)

I’ve logged this issue with vwout via their GitHub page, but can anyone confirm if they have something (file/folder) under cmh-ludl called openLuup_reload_for_docker ?

I’m assuming that’s it’s looking for a specific (.json?) file of some description? If it is, would it be possible for someone to share a example of what the have ?

Many thanks

[akbooer]

That file looks like this:

#!/bin/sh
#
# Dockerized openLuup startup script with reload loop for openLuup
# based on openLuup_reload @akbooer, Aug 2015
# you may need to change ‘lua’ to ‘lua5.1’ depending on your install

openLuupShutdown()
{
  echo "Requesting openLuup shutdown"
  wget -q -O /dev/null "http://localhost:3480/data_request?id=exit" >> /dev/null 2>&1
}

# Capture the shutdown signal and call the luup shutdown URL call to abort the loop
trap openLuupShutdown EXIT INT QUIT TERM

# Strip parameter automatically added by Docker
if [ $# -gt 1 ]; then
  if [ "$1" = "." ]; then
    shift
  fi
fi

tail -F logs/LuaUPnP_startup.log &
tail -F logs/LuaUPnP.log &

# Run openLuup as long as the return code indicates a reload
lua openLuup/init.lua $@
result=$?

while [ $result -eq 42 ]
do
   echo "$(date) Reload openLuup"
   lua openLuup/init.lua
   result=$?
done

exit $result

It's a shell script. But if there's nothing in your folders, it sounds like you'll be missing other things too.

[parkerc]

Thanks @akbooer - is that file simple called openLuup_reload_for_docker - no extension, or do I put .sh at the end ?

[akbooer]

It doesn’t really matter, but it does need to have the executable permission.