diff options
| author | spmfox <spmfox@foxwd.com> | 2024-05-28 15:27:24 -0400 |
|---|---|---|
| committer | spmfox <spmfox@foxwd.com> | 2024-05-28 15:27:24 -0400 |
| commit | 898d4673219d16a5dc19e523f94eba952365f0c1 (patch) | |
| tree | 1065b5713876e4e0d6f2923412fbb5623df10b0f /README.md | |
| parent | db610a23f49958d98858705f20fd63208d7937c9 (diff) | |
removing the base centos-bootc deployment, it caused problems with the final deployed image and did not save disk space
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -35,8 +35,8 @@ This Ansible automation uses bootc to create "the perfect" KVM hypervisor with Z ## How It Works ### Deploy 1. A new or existing system must exist. This system should be as small as possible because its filesystem will persist in the resulting deployed machine -2. A "base" centos-bootc is used for the first deploy - the user SSH key is set for the root user now -3. Once the base is deployed, we use that to build and ```bootc switch``` into the final BootcBlade image +2. ```bootcblade.containerfile``` is copied to the existing system, then ```podman build``` is used to build the image +3. Once the image is built, the BootcBlade image is deployed to the system - then it is rebooted 4. Ansible creates the user with (or without) the password and adds the SSH key ### ISO |