SOLVED ./cloudron-setup script fails to install on dedipath.com VPS Ubuntu 20.04
Lonkle last edited by girish
I tried a regular install, and nothing. Then I did a good ol'
sudo apt update && apt-get -y upgradebeforehand and then Cloudron's script gets further in the process until it dies (something about
linux-image-5.4.0-74-generic) and when it does so does
apt-get -y upgrade(it dies with the same error every time it's run) - like something odd happens with the kernel there. Here's the error:
Setting up build-essential (12.8ubuntu1.1) ... Processing triggers for systemd (245.4-4ubuntu3.7) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for libc-bin (2.31-0ubuntu9.2) ... Processing triggers for initramfs-tools (0.136ubuntu6.5) ... Processing triggers for resolvconf (1.82) ... Processing triggers for linux-image-5.4.0-74-generic (5.4.0-74.83) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.4.0-74-generic I: The initramfs will attempt to resume from /dev/null I: Set the RESUME variable to override this. E: /usr/share/initramfs-tools/hooks/fixrtc failed with return 1. update-initramfs: failed for /boot/initrd.img-5.4.0-74-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-5.4.0-74-generic (--configure): installed linux-image-5.4.0-74-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-5.4.0-74-generic E: Sub-process /usr/bin/dpkg returned an error code (1)
It looks like
sudo chmod -x /usr/share/initramfs-tools/hooks/fixrtcmay have fixed my issue after running into this error both in 18.04 and 20.04 on DediPath. Got a little farther in setup. Now I have to debug this:
Setting up libfuse2:amd64 (2.9.7-1ubuntu1) ... Setting up grub-common (2.02-2ubuntu8.23) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Setting up grub2-common (2.02-2ubuntu8.23) ... Processing triggers for systemd (237-3ubuntu10.48) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Processing triggers for install-info (6.5.0.dfsg.1-2) ... Processing triggers for libc-bin (2.27-3ubuntu1.4) ... sed -e 's/^GRUB_CMDLINE_LINUX="\(.*\)"$/GRUB_CMDLINE_LINUX="\1 cgroup_enable=memory swapaccount=1 panic_on_oops=1 panic=5"/' -i /etc/default/grub sed: can't read /etc/default/grub: No such file or directory
sudo apt-get --reinstall install grub-pcfixed that. I think it's finally going to install. NICE!
sed: can't read /etc/default/grub: No such file or directory
This happens at times when the VPS is really LXC instead of KVM. Cloudron does not support LXC.
@girish Interesting, well, I def got it installed. I only use Cloudron for experimenting and dev-ing but I'm curious what running on an "unofficial" platform now might make me run into (if you know)?
@lonkle TBH, we don't really test on any system other than ubuntu. Most likely other platforms don't work. Even on ubuntu derivatives like mint, it is known to not work.
d19dotca last edited by d19dotca
Just an FYI for anyone else who sees this thread, I ran into a similar issue ("sed: can't read /etc/default/grub: No such file or directory") today when trying to setup an instance on a new provider (Websavers.ca), and in their instance it's using OpenVZ (not LXC, so I presume this is still supported), and I still had to install GRUB before hand with these two commands:
sudo apt-get update -y
sudo apt-get install -y grub-pc
Edit: Just saw a note on https://docs.cloudron.io/installation/ saying this is unsupported. So I guess I won't be able to continue in this direction for production.