Skip to content

feat(runtime): allow overriding the QEMU container image - #3253

Open
6eanut wants to merge 1 commit into
kernelci:mainfrom
6eanut:feat/qemu-docker-image
Open

6eanut wants to merge 1 commit into
kernelci:mainfrom
6eanut:feat/qemu-docker-image

Conversation

@6eanut

@6eanut 6eanut commented Oct 22, 2026

Copy link
Copy Markdown

Use qemu_docker_image from job or platform parameters while retaining kernelci/qemu as the default. Document configuration and cover generated LAVA jobs with regression tests.

Fixes #2591

Use qemu_docker_image from job or platform parameters while retaining kernelci/qemu as the default. Document configuration and cover generated LAVA jobs with regression tests.

Fixes kernelci#2591

Signed-off-by: Jiakai Xu <jiakaiPeanut@gmail.com>
@nuclearcat

Copy link
Copy Markdown
Member

Thanks, this looks straightforward and addresses the use case described in #2591. Is that requirement still active in a lab you work with? Have you tried this on a real LAVA worker with an alternative registry? A successful job link, ideally using a mirror of the existing image, would help validate the end-to-end behavior.

@6eanut

6eanut commented Oct 23, 2026

Copy link
Copy Markdown
Author

Thanks for your review! @nuclearcat

  1. This fix is based on the use case in Allow custom container registry in the qemu boot method for LAVA TestJob template #2591. I can't confirm whether a production lab still needs it.
  2. I set up a local LAVA environment and successfully tested both the default image and a mirror in an alternative registry, including a cold-cache run.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow custom container registry in the qemu boot method for LAVA TestJob template

2 participants