Thank for the update.

=>  PREV_DOLIBARR_VERSION=`php /app/code/htdocs/install/get-version.php`

Log:

2026-02-07T13:35:00Z ==> Starting Dolibarr
2026-02-07T13:35:03Z #0 /app/code/htdocs/core/class/conf.class.php(561): DoliDBMysqli->query()
2026-02-07T13:35:03Z #1 /app/code/htdocs/install/get-version.php(28): Conf->setValues()
2026-02-07T13:35:03Z #2 {main}
2026-02-07T13:35:03Z PHP Fatal error:  Uncaught Error: Call to a member function query() on false in /app/code/htdocs/core/db/mysqli.class.php:355

A shell script with set -e stops when If an error occurs. The script does not have an error handling in such cases, therefore the lock file is still in /tmp.

With error handling

trap 'echo "Houston we have problem"; [[ -f /tmp/install.lock ]] && mv /tmp/install.lock /app/data/dolibarr/install.lock; exit 1' ERR

I thought this issue has been fixed, but we always have the issue. (which is a security one)
I do not know why the Cloudron Dolibarr app runs the cron as root and not as www-data user.

The code could also be adjusted to copy vs move the file so it stays available. But, it's probably moved for a reason I am not aware of.

got same behavior tonight, after ubuntu reboot for security updates (clicked from notification panel, red button "Reboot", all my 26x Dolibarr instances restarted without putting the install.lock file back in place.

I recreate all of them at one using this in shell on cloudron :

#!/bin/bash

BASE_DIR="/home/yellowtent/appsdata"

for appdir in "$BASE_DIR"/*; do
    if [ -d "$appdir/data/dolibarr" ]; then
        LOCKFILE="$appdir/data/dolibarr/install.lock"
        if [ ! -f "$LOCKFILE" ]; then
            echo "Create $LOCKFILE"
            touch "$LOCKFILE"
        else
            echo "$LOCKFILE already exist"
        fi
    else
        echo "no dolibarr in $appdir"
    fi
done

dunno what I should do to see why it doesn't work appropriately

thanks for any help !

Maybe you have seen this behavior at the exact moment the app started.
But, the file should be moved back into place after the app is fully started.

I recreate them by hand (touch install.lock from ssh in OS, maybe I shouldn't to that...?).

On a later update ubuntu, they vanish again.
If I manually reboot (i.e command "reboot" in shell), they're gone too after the reboot.

I dunno where to look at to see exactly what's happening. Is it container side ? or OS side ?
Provided above logs are from container side and there is nothing about the lock file...

Sadly I was not able to reproduce this behavior.

@Crush33 are you using any volumes for the Dolibarr app?

In your provided logs I could not find anything related to the startup of the app and the install.lock file.
Do you have the full app log from the dashboard of the day this happened?
Especially the startup part is important.

The Dolibarr app runs a setup() function on startup that check if the file /app/data/dolibarr/install.lock exists, moves it to /tmp/install.lock and after running the upgrade hooks it should move back the /tmp/install.lock to /app/data/dolibarr/install.lock.

There might have been a failure when running the upgrade hooks or the app crashed or OOM resulting in /tmp/install.lock not being moved back to /app/data/dolibarr/install.lock?
I will try to force such a scenario and see if I can reproduce this behavior.

Error
You do not have enough privileges for this action.