I have an autoinstall on a custom 20.04 ISO I'm building using Cubic. Subiquity is writing a Curtin log and providing a path but I can't for the life of me work out how to break into a shell. This has happened after cloud-init has run.
I have an autoinstall on a custom 20.04 ISO I'm building using Cubic. Subiquity is writing a Curtin log and providing a path but I can't for the life of me work out how to break into a shell. This has happened after cloud-init has run.
I hit the key combo
Alt-F2
and get a shell. This works with both the legacy and live installers. Subiquity logs will be in/var/log/installer
. The key comboAlt-F1
will take you back to the installer UIIt looks like you hit the point where subiquity generates a config for curtin. Either subiquity is failing to generate the config or curtin is failing with the provided config
When using Subiquity Live Server installer (NOT the Desktop installer):
When finished with the shell, the command
exit
will return you to the Subiquity installer.There's only one tty: You cannot run Subiquity and a shell on different ttys.