Simply to report, probably a unique case, but just in case
Today I spin up a new Ubuntu 18.04LTS at Hetzner than launch the
cloudron-setupwhich failed and not
/var/log/cloudron-setup.logfile has been created.
I relaunched the installation script then went to a second terminal to tail the log to discover than the installation was failing simply because this file was missing
I easily resolve the case with
My point is, this might happen to someones else and this someone else might feel cloudron is not ready/mature simply because he/she is not able to install it.
why the installation has to fail if the sed doesn't work on that file?
at the end it is not really a big thing.
would it be better to look if the file exist and if not simply create it ?
had the same issue, @nebulon already fixed that two days ago: https://git.cloudron.io/cloudron/box/-/commit/23474c97528893dbc25b47d68441d3cc0c6de6b3
Thank for the reply, it is always nice to not feel alone with specific issue