Read the statement by Michael Teeuw here.
MagicMirror Container
-
@plainbroke container is a mini OS/Application bundle. (same as an SD card with all the stuff installed)
you run it in the docker runtime.
there are commands to run one docker image to container (docker run)
and commands to run a list of them as a big application set (docker compose)for MM, there is good news and bad news…
good, easy to get up and running the post install level,
docker run or docker compose(Karstens image) … up it comes…bad, adding modules gets harder… you need to use docker commands to get INSIDE the container to do git clone, npm install… etc
best to add some tool to do module install, MMPM, my MMM-Config, MMM-RemoteControl. then you get a web page to work from instead of having to get inside the container.
-
@sdetweil You provide your own list of modules and config alongside your compose and it all gets imported into the container. No need to go fiddle in the container itself.
-
@mumblebaj in yours… if you know ahead of time. …
its just different work… all the work is the same.
-
@sdetweil Agreed, all work is the same.
-
@mumblebaj @KristjanESPERANTO @sdetweil
Thank you all for the information. I think I will stick with the way I already understand. setting up the docker and all seems like more work that is not in my wheelhouse. Interesting approach to the same end result.
