thank you for the reply . docker not something I used particularly much. and just something I was experimenting with lately . in my effort of build small contained devices within the openwrt opensource router format
okay I think perhaps I know why it does not work - emoncms is not particularly build for my architecture. arm7 —wondering if they are willing to add in different architectures when building docker container. as it removing alot of different devices the docker container will work with.
example output from openwrt docker “inspector” it reports using arm7 build
perhaps if @glyn.hudson does up load different archs he could follow home assistants build policy that way people can load to different architectures easily and be able to interface with home assistant if they want
to bad , if true, they do have a fairly big download base as a docker base over million pulls … no worries maybe if I feel energetic maybe I will build a docker container for oem. I just have to figure out how. giving opensource router bases out there that run across 1000’s of different devices and the newer multi core risc-v 8 core 2 ghz opensource router bases that starting to appear
if you want to try the one I made a couple months ago though i do not use emoncms. it seams to work and does not crash you have to create a maria database for it locally outside the docker https://hub.docker.com/r/sash999/emoncms_localdb/tags
just follow the same directions as it is in openwrt
Is that an issue for you? I’m pushing a few updates to tidy things up so if there is an issue, let me know (GitHub or new thread). I used them recently to create a new LXC container and all was fine.
well chroot, not basic. it allow you to install another linux os software layers on top of another one of any flavour even incompatible software version ie: in my case openwrt host but running debian software on top of it . if you mess up, simply delete the chroot folder and start again . does not interfere with your other os. you are able to run the two different flavours software as if was part of the same system… also unlike docker, it only runs when ever you call on the software and nothing is loaded into memory until then and then the only thing loaded into memory is the software itself (ie say I run VLC or mplayer which openwrt does not support to play internet radio stations ( part of my AI function ) … it can have easy connection to your /dev folder and have direct access to all your devices or even folders but general it does not, it fully independent of the host computer . you can easily rebuild the chroot in 5 minutes . as currently, my openwrt router is now also AI and whisper ASR speech to text server and translator ( i really squish alot into my little 5w openwrt routers might have to start looking for a openwrt router that has CUDA GPU lol so I can get speech to text translations down to a second or less instead of the current 10 seconds ) basically it how all android phones run the os under neath and chroot for the user interface on top- that is what jailbreaking about on android phones breaking out of chroot to get to the OS underneath
Thanks @stephen and @Bill.Thomson but I’ll give chroot a miss - got enough on just setting everything up in the new house, without having to wrestle with something new.
no worries - good luck in the new house
heck if you or someone feel energetic one day here’s a basic setup for chroot that installs vlc, git, vim, nano, curl and build essentials
#!/bin/sh
## your build directory
THIS_CHROOT="/root/bullseye"
#chroot is not there, build it change the arch to match yours ie armh amd64 arm64 etc....
if [ ! -d "$THIS_CHROOT" ]; then
debootstrap --arch amd64 bullseye "$THIS_CHROOT"
chroot "$THIS_CHROOT" /bin/bash -c "apt install -y curl build-essential git vim nano vlc"
fi
chroot "$THIS_CHROOT" /bin/bash -c "mount -t proc proc /proc && \
mount -t sysfs sys /sys && \
apt-get install -y vlc "
there use to be a Debian build script for emoncms, but I can not find it. I would’ve adjusted the above for you to build if you wanted chroot to have direct access to your /dev directory.
mount -o bind /dev /chroot_build_dir/dev
similar if you want access to local, you could link a directory in local.rc
you initialize it with:
chroot /root/your-build_dir bash /root/run.sh
then inside your_build_dir you have something like this
#!/bin/bash
function cleanup {
echo "Inside: cleaning up 🧹"
umount /proc
umount /sys
}
trap cleanup EXIT INT
mount -t proc proc /proc
mount -t sysfs sys /sys
execute some_prorgam/sevices || exit 1
exit 0
thank you for the reply, it does not support my architecture unfortunately only supports amd64… do you have a basic debian install script - I could install using chroot or directly on my various architectures that i use