Cloudron Forum

I like the idea. For lack of a better name, let's call this "lock/unlock" app containers.

Container starts locked. When unlocked:

It will make the container rw Disables automatic updates Gives warning to user that all changes will be lost when updating and are not part of any backups Automatically starts up the container (unlike debug mode which keeps the container in paused mode).

I think this gives the customer a window to "hotfix" things until upstream (or packaging team) figures out some fix.

It seems that one can setup an "automount" that will make systemd automatically mount when a mount is accessed . It's unclear if this also applies to mount failures or just "not ever mounted". If someone wants to try, I think we need something like this:

The systemd unit file must be named systemd-escape -p --suffix=automount <HOSTPATH>

Then, create a file /etc/systemd/system/<unit_filename_from_above_command>:

[Unit] Description=Automount of hostpath [Automount] Where=HOST_PATH_HERE [Install] WantedBy=multi-user.target systemctl enable <unit_filename>

If that works, I can put this in our code (for volumes and backups).

@holm yes, thanks. This is planned but with a slightly different approach. The restore process will keep track of what it's downloaded, so that the download can be incremental. That way, one ideally doesn't need to select anything.

@avatar1024 hopefully now it gets a good kick 🙂

What you say, @girish ?