System has not been booted with systemd as init system (PID 1). Can’t operate.
Failed to connect to bus: Host is down
Failed to talk to init daemon.
@masteritua also for this one I’ve sent the link to some more technical profiles.
The Ubuntu solution deployed from 3Bot is a container. Unlike VMs, containers do not respond to the reboot command because they are not a full OS. The usual pattern for cases where you might have rebooted a VM is to replace the container with a new container. Of course, this means that any changes to the container are lost.
To make persistent changes to a container, you’d need to generate a new image (for example, using Docker on your local machine to shapshot changes to an image, then uploading that image to the flist hub). Or if it’s data generated at runtime that you need persisted, attaching a volume mount is an option. Note though that the volume option in 3Bot’s generic flist chatflow only lasts as long at the container you are deploying. To achieve persistence across deployments, you’d need to use the JS-SDK directly.