### Check existing issues - [x] I've verified that this request isn't described by any existing issues. ### Request ## Summary Several Rockcraft tutorials hardcode `amd64` in the `rockcraft.yaml` `platforms:` block and in the resulting `.rock` filenames used by later commands. A reader on an `arm64` host (e.g. Apple Silicon macOS, which is the majority of current Macs) packs a `..._arm64.rock` file, so the copy-paste `skopeo` import commands which reference `..._amd64.rock`, and this fails with a file-not-found error. ## Steps to reproduce ### Environment - Host architecture: `arm64` (Apple Silicon) - Build VM: Multipass (Ubuntu 24.04) - Docs version: `1.19` ### Reproduction: Using "Pack a Python package" as the clearest example: 1. In "Setup your environment," select the **macOS** tab (as an Apple Silicon user would). 2. Follow through to the `rockcraft.yaml` snippet: ```yaml platforms: arm64: ``` 3. Run `rockcraft pack` on the `arm64` host/VM. 4. Observe the produced file is `pyfiglet_0.7.6_arm64.rock`. 5. Run the import command exactly as written: ``` sudo rockcraft.skopeo --insecure-policy copy oci-archive:pyfiglet_0.7.6_amd64.rock docker-daemon:pyfiglet:0.7.6 ``` → fails, because the file on disk is `..._arm64.rock`. The Hello World and Chisel tutorials reproduce the same way with their respective filenames. ## Suggested fix Apply one consistent approach across the affected tutorials, changing from ``` sudo rockcraft.skopeo --insecure-policy copy oci-archive:hello_latest_amd64.rock docker-daemon:hello:latest ``` to something that use $(dpkg --print-architecture) like ``` sudo rockcraft.skopeo copy \ --insecure-policy \ oci-archive:hello_latest_$(dpkg --print-architecture).rock \ docker-daemon:hello:latest ``` ### Document location https://documentation.ubuntu.com/rockcraft/1.19/tutorial/hello-world/