-
-
Notifications
You must be signed in to change notification settings - Fork 691
docs: step-by-step scaleway documentation to get an image #11429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Add comprehensive documentation for deploying Talos on Scaleway cloud platform. Signed-off-by: Adrien Ruellou <ruello_a@modulotech.fr>
|
||
1. **Download the ISO image** of the Talos version you wish to run: | ||
```bash | ||
wget "https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/v{{< release >}}/scaleway-amd64.iso" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are you sure it's an ISO?
it feels like it should be a disk image
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah totally, that's the only way i had to make it work, with .raw.zst
it never worked for me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is very strange, as it contradicts previous instructions, and it doesn't make much sense to me, as ISO is not something you can put as a disk to the VM, it's only a temporary one-time way to boot.
I think something is wrong here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With .raw.zst image disk, i can boot the node and initialize it, but when i reboot the instance, it never find the boot disk:
BdsDxe: failed to load Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x3,0x0)/Scsi(0x0,0x0): Not Found
BdsDxe: failed to load Boot0002 "UEFI SCW sbs " from PciRoot(0x0)/Pci(0x3,0x0)/Scsi(0x1,0x0): Not Found
BdsDxe: failed to load Boot0003 "UEFI SCW sbs 2" from PciRoot(0x0)/Pci(0x3,0x0)/Scsi(0x2,0x0): Not Found
BdsDxe: failed to load Boot0004 "UEFI SCW sbs 3" from PciRoot(0x0)/Pci(0x3,0x0)/Scsi(0x3,0x0): Not Found
BdsDxe: failed to load Boot0005 "UEFI SCW sbs 4" from PciRoot(0x0)/Pci(0x3,0x0)/Scsi(0x4,0x0): Not Found
>>Start PXE over IPv4.
A problem i don't have with iso file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is odd, as if I understand correctly, the disk image should be on your disk by this time. But not an expert in Scaleway in any sense
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah it should ! But i don't know why, it's not found 🤷♂️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello, for the reboot issue with .raw.zst
image, I opened an issue here siderolabs/go-blockdevice#134
I think we should be able to avoid using ISO images when it's fixed.
Pull Request
What? (description)
Add comprehensive documentation for deploying Talos on Scaleway cloud platform.
Why? (reasoning)
Scaleway is a supported cloud platform for Talos but was previously undocumented. This creates a barrier for users wanting to deploy Talos on Scaleway (like me)
Acceptance
Please use the following checklist:
make conformance
)make fmt
)make lint
)make docs
)make unit-tests
)