Lorenzo Aiello

Solved.

Turns out my own mucking with the "conf_global.php" was my demise. Not sure what, or how it happened, but it was missing the "installed" key in $INFO array. Setting it with a true bool value fixed the issue. 🤦‍♂️

I've searched the forums but I'm having trouble finding the answer I'm looking for, and I realize I'm doing something that isn't really supported.

How does IPS know when the install is "finished"? Is there a lock file or something put somewhere?

For context: I'm trying to bake a docker container with IPS in it (Cache in Redis, Filesystem in S3, so it shouldn't need any persistent local storage...in theory). I can run the installer successfully, but as soon as I restart the container with the generated "conf_global.php" included/mounted, it shows me this:

I've tried running "find . -type f -printf "%C@ %p\n" | sort -rn | head -n 50" to see what files it's recently manipulated after an install, but I'm not seeing anything interesting.