I missed this discussion on Docker, and I just noticed the latest changes discussed here were pushed and one of them broke my jeedom installation and my Docker images
(I’m the author of nricheton/jeedom-optimized which pre-installs several dependencies : https://github.com/nricheton/jeedom-docker-optimized)
Here is my feedback :
- APACHE_PORT :
This env. variable was used mainly for plugins which requires to use network broadcast (Homebridge for instance). Internally this is for the avahi daemon and service discovery.
When you want to use these plugins, you have to launch docker image in host networking mode. In that case, you cannot redirect ports so you NEED to be able to change apache port if you already expose port 80 somewhere.
Please restore APACHE_PORT, without it you cannot use homebridge in jeedom with docker with another http server (TLS proxy for instance). In the meantime, I’ll do a workaround in my images.
- MODE_HOST :
Not sure what it was doing, +1 for removal
+1 for removing SSH access to images. Preferred way is
docker exec -it bash
+1 for removing DB from container.
- Image management
In the docker mindset, images are versioned and you are expected to redeploy images on frequent basis, at least for security fixes. You should be able to destroy / recreate image at will without any impact.
With the plugin/marketplace system, plugins should be installed and updated on docker volumes so they can persist when image is recreated.
But in an ideal world, jeedom files (except configuration) should be included in docker image, tagged with versions. I didn’t go on this path yet.
My current strategy is to at least install most plugin dependencies in Docker image, so you don’t have to launch dependency install for every plugin when you create a new image. This is the reason behind the image nricheton/jeedom-optimized. (+ dist-upgrade, frequent rebuilds for security)
You should try nricheton/jeedom-optimized:rpi-latest instead of nricheton/jeedom-optimized:latest. It is compiled for Raspberry
** Jeedom on docker ** :
On my side, I have no issue with all my plugins on docker (wave, mobile, homebridge, etc…).