I set up the service packaging environment according to the offical docs (Environment Setup - Service Packaging), but when checking the versions of all components at the end, I always get the message “start-cli: not found”.
Even tho after running the automated installer script it says “Installation succesful” and “start-cli is ready”.
Any ideas on how to get it working?
Information about my setup:
I tried installing it inside a Kapsule container (Ubuntu 26.04 LTS) on KDE Linux (immutable/atomic distro).
Still doesn’t work.
In my container source ~/.bashrc outputs source: not found.
In my immutable enviroment it works and displays the correct start-cli version then, but there npm install and make obviously don’t work.
I didn’t actually catch that on your original post, the immutable/atomic part. It would seem you’ve made something of an explicit choice not to be able to make this a hackable dev device. Perhaps set up a working dev environment, even if a VM?
There are some benefits to immutable distros and I was hoping for Kapsule to be suitable to still get dev work done.
I brought the problem up in the KDE forum as well now and am in contact with the developer of Kapsule to maybe see if we can get it working or if it would be necessary to change something about Kapsule to fit this use case.