So the way containers get uploaded to a repository is we map the variant name of the image in the compose to a repository name. Looking at the latest ELN compose the aarch64 toolbox as the following properties:

{
    "arch": "aarch64",
    "bootable": false,
    "checksums": {
        "md5": "918a178bfa1cb2dffc7a7b7b965901ef",
        "sha1": "acf620ff14e12cc42c144808482b6374a5c0eb27",
        "sha256": "68fb3cf0e0c54a14be5b17fbd50152d87301f8cd004de5ccc7199564eb128a75"
    },
    "disc_count": 1,
    "disc_number": 1,
    "format": "tar.xz",
    "implant_md5": null,
    "mtime": 1758552266,
    "path": "AppStream/aarch64/images/Fedora-ELN-Container-Toolbox-11-20250922.n.2.aarch64.oci.tar.xz",
    "size": 266115720,
    "subvariant": "AppStream",
    "type": "container",
    "volume_id": null,
    "variant": "AppStream",
    "url": "https://kojipkgs.fedoraproject.org/compose/eln/Fedora-eln-20250922.n.2/compose/AppStream/aarch64/images/Fedora-ELN-Container-Toolbox-11-20250922.n.2.aarch64.oci.tar.xz",
    "direct_url": "https://kojipkgs.fedoraproject.org/compose/eln/Fedora-eln-20250922.n.2/compose/AppStream/aarch64/images/Fedora-ELN-Container-Toolbox-11-20250922.n.2.aarch64.oci.tar.xz"
}

Other containers we upload have clearer variants, like the Fedora toolbox has the "Container_Toolbox" variant. Maybe "AppStream" is actually the variant you want, but we should make sure the variant is correct before adding the mapping to the config in the Fedora infra ansible repo

Thank you for the explanation. We have updated our variants and sub-variants.
The image should now have the variant "BaseOS" and the sub-varient "container-toolbox"

Is that correct to get it into quay.io/fedora/eln-toolbox ?

Also, our existing images now have subvariants too, will you need to update for that?

Thank you for the explanation. We have updated our variants and sub-variants.
The image should now have the variant "BaseOS" and the sub-varient "container-toolbox"

Is that correct to get it into quay.io/fedora/eln-toolbox ?

The final step is to update the map in Ansible. Someone with permissions will need to create the quay.io/fedora/eln-toolbox repo before doing that, though, since the service expects target repositories to exist from what I remember.

Also, our existing images now have subvariants too, will you need to update for that?

If the subvariant changed from "BaseOS" to something else that'll need to be updated in Ansible as well.

I have made the repo on quay.io.

We can merge that existing PR, or if we want to also switch to the subvariant/variant at the same time someone could pr that?

Also, I don't know if @adamwill needs to adjust anything on the openqa side for this.

Both quay.io/fedora/eln and quay.io/fedora/eln-toolbox are getting uploads now, thanks.

However, the cloud images are not getting updates, which will require a separate change: https://pagure.io/cloud-image-uploader/pull-request/63

Both quay.io/fedora/eln and quay.io/fedora/eln-toolbox are getting uploads now, thanks.

However, the cloud images are not getting updates, which will require a separate change: https://pagure.io/cloud-image-uploader/pull-request/63

Merged and deployed so the next compose should resume uploads.

I have made the repo on quay.io.

We can merge that existing PR, or if we want to also switch to the subvariant/variant at the same time someone could pr that?

Also, I don't know if @adamwill needs to adjust anything on the openqa side for this.

Tweaking the config should be self-contained to the image uploader, and is really just to make the config clearer and easier to maintain long-term. I've filed https://pagure.io/cloud-image-uploader/issue/64 to track it.

yeah, openQA is fine. I would have needed to update the scheduler if the subvariant for tested images had changed, but it didn't.

(note: I tend to ignore variant entirely and only go on subvariant, I've never yet found a case where it was necessary or useful to take the variant into account).