You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assuming the following, that someone runs the scripts/library on a docker installation or re-running it after already performing an installation. It would be nice if the installer could run again and run different profiles scenarios. But that requires the mount points to be pointed towards the correct place.
Which, perhaps the archinstall.Installer() should take care of.
The text was updated successfully, but these errors were encountered:
Clarification: If something happens during the installation, archinstall.Installer() should not re-mount or re-open encrypted drives during a re-run. Or perhaps a template should be created called python -m archinstall patch --packages=XXX --mountpoint=/mnt. (Just a thought I wanted to put down)
Putting this on the back burner for now as the point of it is getting less and less relevant hehe.
Creating a example-profile that does the workload sounds more appealing.
Assuming the following, that someone runs the scripts/library on a docker installation or re-running it after already performing an installation. It would be nice if the installer could run again and run different profiles scenarios. But that requires the mount points to be pointed towards the correct place.
Which, perhaps the
archinstall.Installer()
should take care of.The text was updated successfully, but these errors were encountered: