-
Describe the solution you'd likeI wonder how to add RaspberryMatic to an existing Raspberry Pi (e.g. with customized OS, other webservers, DBs etc running on it), either as a native package or as a lightweight container. IMHO, there is no native installation as a package for aarch64. IMHO, there is no lightweight VM suitable for a rpi4. So: Wouldn't it make sense to use systemd's machines aka lightweight containers aka systemd-nspawn to run RaspberryMatic on a Raspberry Pi? To recall: E.g. you may simply unpack virtually any linux OS on your host e.g. in I believe, the only thing required was:
What do you think? Describe alternatives you've consideredI don't believe it makes sense to run Qemu or Docker on a rpi4 to run RaspberryMatic in it. Is your feature request related to a problem?This feature could help saving one extra Raspberry Pi for RaspberryMatic (if you already run a Raspberry Pi for another reason). Additional informationNo response |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
This is not an issue but a problem/support item that should be rather moved to the discussion part of the github repo. Issue Tickets should just be opened for potential enhancements or bugs... |
Beta Was this translation helpful? Give feedback.
-
I would suggest you read more documentation and walk into the topic more deeply before asking such questions which thousands of other people have already asked or answered in the past. So simply walk yourself through the official documentation, see here: https://github.com/jens-maus/RaspberryMatic/wiki/Installation And then have a look at the virtual installation options RaspberryMatic already provides and I am sure you will find one of these virtualization options useful for your case: https://github.com/jens-maus/RaspberryMatic/wiki/Installation#grundinstallation-virtuell And if you really require a lightweight virtualization like LXC, have a look for that installation option as well: https://github.com/jens-maus/RaspberryMatic/wiki/Installation-LXC Nevertheless, please note that the best practice for installing RaspberryMatic in a virtualized way is the use of ProxmoxVE either on a adequate x86-based system or even on a RaspberryPi4 or RaspberryPi5. See here: https://github.com/jens-maus/RaspberryMatic/wiki/Installation-Proxmox-VE So there should really be everything pretty much explained. Just take your time on walking through all that documentation which already exists since a long time. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the quick response. I am sorry to have asked via issues/bug tracker. Please look, I just followed what was advised at the very bottom here: https://github.com/jens-maus/RaspberryMatic/wiki/Support#featurerequests It directs to the issue/tracker in case of feature requests. And I also don't see my question to be addressed by "thousands": There is zero output for "systemd-nspawn" or "machinectl" and such. Anyway: In case you have worked with systemd's containers you might see the difference I am addressing here. There is ZERO overhead, setup etc to run a virtualized machine. LXC and others still require significant changes on the host. Maybe I can help myself installing RaspberryMatic via SD card or similar on a separate rpi, and then copy over the OS into a systemd machine. |
Beta Was this translation helpful? Give feedback.
I would suggest you read more documentation and walk into the topic more deeply before asking such questions which thousands of other people have already asked or answered in the past.
So simply walk yourself through the official documentation, see here:
https://github.com/jens-maus/RaspberryMatic/wiki/Installation
And then have a look at the virtual installation options RaspberryMatic…