Comment 5 for bug 2060442

Revision history for this message
panreyes (panreyes) wrote :

I'm not sure if this is the same bug, but in my case the installer was not able to complete the installation, and kept on the same message "curtin command target-in".

I "completed" it by executing 'killall -9 unattended-upgrades'

I'm not sure if this is related to the installer being a beta debug version or not, but it didn't complete after 16 minutes. I was installing it in a VirtualBox VM on a pretty fast CPU (4x cores from a Ryzen 7 5800X), with NVME storage, 16GB of RAM and 1gbps internet connection (actually 10gbps, but I still have to upgrade a switch).

This happened selecting the 3rd party drivers option and it also happened without that option.

Here's a small excerpt of the subiquity-server-debug.log:
2024-04-22 23:20:53,297 DEBUG root:38 start: subiquity/Install/install/postinstall/run_unattended_upgrades/cmd-in-target: curtin command in-target
2024-04-22 23:36:55,887 ERROR subiquitycore.utils:209 Unattended upgrades exited with result: 1

I wonder if it just was updating my system, but because I had no feedback from the installer I couldn't tell.