add example for BSD images to system-imaging module - #191
Merged
Conversation
naddinadja
force-pushed
the
nuageinit
branch
7 times, most recently
from
August 14, 2025 08:18
94b3d21 to
2f6dedc
Compare
naddinadja
changed the title
Contributor
Author
|
@safl the FreeBSD image is very large, and this PR fails with "System.IO.IOException: No space left on device" from the Github Runner .... Should we just not test the FreeBSD image, or can we increase the memory size? |
Before, the image path was only replaced with the decompressed_path if the script performed the decompression. If the decompressed file already existed, the image path was not overwritten, which lead to failure, as the compressed file was then used as the image (which is not possible). Signed-off-by: Nadja Brix Koch <n.koch@samsung.com>
naddinadja
force-pushed
the
nuageinit
branch
from
September 22, 2025 07:58
99c2cfb to
5a56f85
Compare
nuage-init is the initialisation tool used in FreeBSD images (they call it "basic cloudinit"). This is a subset of cloud-init, and doesn't support all the same features. To support FreeBSD images, we host these images with cloud-init pre-installed and provide the download URL for these in the example config files. Signed-off-by: Nadja Brix Koch <n.koch@samsung.com>
naddinadja
force-pushed
the
nuageinit
branch
14 times, most recently
from
September 22, 2025 13:05
8f6efdb to
62106f3
Compare
The two examples in the system_imaging package were constructed to test all images in the given configs. These examples become comprehensive as we add more and more examples. The purpose was to ensure that all images defined in the config are valid. To not create examples that are so large that they break the CI, we simplify the system_imaging example to just match on the pattern "*debian*", keeping them 'light-weight'. The test of all images in the config is moved to a separate GHA job. This also removes the duplicate example config files in the system_imaging package, so we don't have to maintain to identical files. Signed-off-by: Nadja Brix Koch <n.koch@samsung.com>
naddinadja
force-pushed
the
nuageinit
branch
from
September 22, 2025 13:16
62106f3 to
380267a
Compare
Pull Request Test Coverage Report for Build 17916534130Details
💛 - Coveralls |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
nuage-init is a subset of cloud-init, which is used on the FreeBSD images, so it can't do all the things that cloud-init does, which leads to problems with it not terminating the qemu instance when expected.
We have added the bsd-images repo https://github.com/refenv/bsd-images, where we pre-install cloud-init to BSD images with nuage-init. This PR adds a guest using such an image to the example config files.
Should solve #190