Refactor kci-deploy for improved reliability, structure, and full Docker-in-Docker deployment #228
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR improves the reliability, structure, and usability of the
kci-deploy
tool for local KernelCI deployments.🔧 General Improvements
set -e
) to avoid silently failing steps.expect
invocation: Replaces#!/usr/bin/expect
shebang with a direct call toexpect
, avoiding reliance on system-specific interpreter paths — ensures compatibility across distros (e.g. Fedora Atomic I am using).docker build
steps to reduce complexity and build time..gitignore
to exclude artifacts that shouldn't be tracked.kernelci
repo folder: Prevents accidental inclusion of cloned sources underkernelci/
in Git status/diffs.localinstall/kernelci
folder has been added to the.gitignore
, potentially fixing localinstall/kernelci: This folder shoud be ignored or added as submodule #179.🐳 Migrate
kci-deploy
to a Docker-in-Docker deployment modelThis refactors the deployment approach to use a Docker-in-Docker (DinD) architecture, where all deployment logic — including building and running the actual KernelCI services — occurs within a container.
Instead of installing dependencies locally, users now only need Docker installed on the host. Everything else is self-contained in the deploy container.
Starting a local deploy of the KernelCI infrastructure now means simply running:
without any dependency (other than docker) or any unexpected behavior.
Start/stop commands can be used to stop the local deploy or to start it again:
Notes
kernelci-api
services.