Open ryjogo opened 7 months ago
If you're using a disk image, Talos is already installed, so machine.install
is ignored.
It's counter-intuitive, and might change in Talos 1.7.
Ah! OK so that explains it.. Just to clarify..
/dev/sda is the nocloud image that i have created with packer - i boot and install from /sda with the intention of /sdb being my installation disk, and /sda being my installation medium.
So, talos thinks it is already installed, thus ignores the install settings?
yes, you don't need to install if using a disk image - just write the disk image where you want Talos to run.
Ah! OK so that explains it.. Just to clarify..
/dev/sda is the nocloud image that i have created with packer - i boot and install from /sda with the intention of /sdb being my installation disk, and /sda being my installation medium.
So, talos thinks it is already installed, thus ignores the install settings?
Whoops. I missed this! As mentioned in Slack, the install
section is skipped if Talos is already installed. The nocloud image is "already installed to."
Bug Report
Description
When setting: machine.install.disk: "/dev/sdb" doesn't seem to select the disk. After talking with @andrewrynhard we tried the diskSelector, to which this still did not work.
The disk (32GB) is a fresh, attached disk.
Logs
install.diskSelector is set to >= 20GB - it should select the 32GB disk.
Yet the installation disk is set to /sda which is 17GB
I have tried removing the 17GB disk, to ensure that the 32GB disk doesn't have the installation, and boot fails - thus its not installed on the 32GB disk.
Environment