-
Notifications
You must be signed in to change notification settings - Fork 61
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
devel: add instructions for using the script
Add instructions for troubleshooting using the script to build an image and boot it without BIB.
- Loading branch information
1 parent
61b4e0c
commit b3aef11
Showing
1 changed file
with
15 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
# Troubleshooting build failures | ||
|
||
If your container image fails to build using bootc-image-builder, or if it builds successfully but fails to boot, it's often not clear if the problem lies with bootc-image-builder or the container itself. | ||
|
||
To test building an image without bootc-image-builder, try the [bootc-install](devel/bootc-install) script in this repository. | ||
|
||
**IMPORTANT** | ||
Before running the script, note that it creates a file called `disk.raw` in the working directory. Make sure this action doesn't overwrite any existing files. | ||
|
||
After the disk is created, you can boot test it using qemu. It's best to convert it to a qcow2 image first: | ||
``` | ||
qemu-img convert -O qcow disk.raw disk.qcow2 | ||
``` | ||
|
||
You can then follow the [instructions in the README](README.md#running-the-resulting-qcow2-file-on-linux-x86_64) to test that the image boots successfully. |