feat: Adds option to pull arm64/amd64 examples

[cdrage]

feat: Adds option to pull arm64/amd64 examples

What does this PR do?

• Adds the ability to choose what initial arm64 or amd64 image example
  you want
• Defaults to native architecture when initially loading
• Pulls the architecture correctly

Screenshot / video of UI

Screen.Recording.2025-01-16.at.2.14.53.PM.mov

What issues does this PR fix or reference?

Closes #1154

How to test this PR?

1. Go to examples page
2. Select from the drop down the arch you want
3. Pull the image & build

[deboer-tim]

Need to update the copyright in the .ts files (2024-2025).

Instead of adding isArm() to the API, could we do getArch()? Seems a bit cleaner for future use. (or we could use os.arch() in the frontend?)

[cdrage]

Need to update the copyright in the .ts files (2024-2025).

Instead of adding isArm() to the API, could we do getArch()? Seems a bit cleaner for future use. (or we could use os.arch() in the frontend?)

We don't have getArch in the PD API, so instead I've added isArm and used the already-added isX86.

At the moment the only other arch that we could possibly support is x390 but I'm unsure what the status of that is.

I've updated the code / tests!

[deboer-tim]

Need to update the copyright in the .ts files (2024-2025).

Thanks for updating!

Instead of adding isArm() to the API, could we do getArch()? Seems a bit cleaner for future use. (or we could use os.arch() in the frontend?)

We don't have getArch in the PD API, so instead I've added isArm and used the already-added isX86.

At the moment the only other arch that we could possibly support is x390 but I'm unsure what the status of that is.

But why not just expose a getArch() function directly, that just returns the value from os.arch [*]? It would be one less function and avoid potentially having to add something like isS390() in the future.

[*] I'm also finding it a bit odd that the UI uses isX86() to decide to default to the 'amd64' arch. One option would be to use the values from os.arch() consistently, but I think it would be cleaner for bootc.ts to include something like export type Architecture = 'arm64' | 'amd64'

Then the API could export one getArch(): Architecture function, and both backend & shared pullImage() functions could have some type safety with arch?: Architecture instead of arch?: string. Sound ok?

[cdrage]

Need to update the copyright in the .ts files (2024-2025).

Thanks for updating!

Instead of adding isArm() to the API, could we do getArch()? Seems a bit cleaner for future use. (or we could use os.arch() in the frontend?)

We don't have getArch in the PD API, so instead I've added isArm and used the already-added isX86.
At the moment the only other arch that we could possibly support is x390 but I'm unsure what the status of that is.

But why not just expose a getArch() function directly, that just returns the value from os.arch [*]? It would be one less function and avoid potentially having to add something like isS390() in the future.

[*] I'm also finding it a bit odd that the UI uses isX86() to decide to default to the 'amd64' arch. One option would be to use the values from os.arch() consistently, but I think it would be cleaner for bootc.ts to include something like export type Architecture = 'arm64' | 'amd64'

Then the API could export one getArch(): Architecture function, and both backend & shared pullImage() functions could have some type safety with arch?: Architecture instead of arch?: string. Sound ok?

Sounds good! I'll update it for that. For some reason I thought you meant adding "getArch" upstream to PD, but I see we don't have anything up there.

I'll add the getArch function and you are right, instead we can just do if / switch statements to determine if something is arm64 / amd64, etc.

[cdrage]

Updated to use getArch instead (in a separate commit) and ready for a re-review! @deboer-tim

[deboer-tim]

Thanks Charlie, this is better!

As per my last comment the one thing I still don't like is how arch is just a string and the frontend needs to understand how to map that string between os.platform arch and container arch. I'd prefer to have BootcAPI getArch() and pullImage() use the same values (probably getArch() does some mapping) so that the UI can use the values directly and never needs code like this:

if (hostArch === 'x64') {
    defaultArch = 'amd64';

but I won't hold this up, we can take it as a follow-up.

[cdrage]

Thanks Charlie, this is better!

As per my last comment the one thing I still don't like is how arch is just a string and the frontend needs to understand how to map that string between os.platform arch and container arch. I'd prefer to have BootcAPI getArch() and pullImage() use the same values (probably getArch() does some mapping) so that the UI can use the values directly and never needs code like this:

if (hostArch === 'x64') {
    defaultArch = 'amd64';

but I won't hold this up, we can take it as a follow-up.

I agree. I'll follow this up in a separate PR.