kernelci / kernelci/kernelci-deploy

Provide prebuilt images for localinstall

Open
#169 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
4
Forks
19
Avg merge
3d 9h
Merged PRs (30d)
3

Description

Currently localinstall provides a way to build all the Maestro components from scratch. Although it's great for educational purposes, some use-cases might depend only on interacting with Maestro instance (without the infrastructure setup step).

In order to do so (and to make it available quickly), localinstall could use prebuilt images (including cached kernel sources) unless forced to rebuild the whole setup from scratch.

An example of this behavior is available in [lava/pkg/docker-compose](https://gitlab.com/lava/pkg/docker-compose) (see [.env](https://gitlab.com/lava/pkg/docker-compose/-/blob/master/.env#L2)):

- prebuilts are used by default
- user can provide specific image/tag
- [rebuild from scratch can be requested demand](https://gitlab.com/lava/pkg/docker-compose/-/blob/master/Makefile#L6)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the localinstall entry point and its current build-from-scratch flow. Compare its behavior with the referenced docker-compose .env and Makefile examples, then define how prebuilts, a user-selected image or tag, and an explicit rebuild request should work. Done means localinstall uses prebuilts by default while retaining an opt-in full rebuild path.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose
Domain
devops, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.