From 526e9f4ab704c39b5b496e81a0c77b375634f60b Mon Sep 17 00:00:00 2001 From: "Alex A. Naanou" Date: Mon, 8 Jan 2024 00:28:42 +0300 Subject: [PATCH] notes... Signed-off-by: Alex A. Naanou --- nextcloud/make.sh | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/nextcloud/make.sh b/nextcloud/make.sh index 229094f..298c312 100755 --- a/nextcloud/make.sh +++ b/nextcloud/make.sh @@ -68,6 +68,26 @@ getLatestTemplate '.*-turnkey-nextcloud' TEMPLATE pctCreate $ID "$TEMPLATE" "$OPTS_STAGE_1" "$PASS" sleep ${TIMEOUT:=5} +# hooking into tkl init process: +# - wait for /etc/inithooks.conf to be generated by: +# /usr/lib/inithooks/firstboot.d/29preseed +# this file existion would mean that the first stage of setup is +# done and we can do: +# lxc-attach $ID -- bash --login exit +# to launch interactive setup... +# XXX can we get console/log output while poling??? +# - inject a script into the chain to do our stuff +# Q: can we reuse tkl's scripts??? +# +# * another strategy would be generate our own inithooks.conf but +# this would require us to mount the ct volume before first boot... +# see: +# https://forum.proxmox.com/threads/pct-push-when-lxc-is-offline.116786/ +# * might be usefull to do both to: +# - maximize compatibility / change tolerance (tkl ui) (???) +# - skip dialogs we do not use... +# ...i.e. poll-patch-ui +# # for tkl inithooks doc see: # https://www.turnkeylinux.org/docs/inithooks