Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

just recipe build-vm does not work #60

Open
SamuelYaron opened this issue Jan 23, 2025 · 2 comments · May be fixed by #62
Open

just recipe build-vm does not work #60

SamuelYaron opened this issue Jan 23, 2025 · 2 comments · May be fixed by #62

Comments

@SamuelYaron
Copy link

Hi,
I am working on my own image based on this template. (Forked 1 week ago)

Unfortunately the just recipes for local testing do not seem to work.

just build-vm
[...]
[-] Manifest generation step
Message: Generating manifest manifest-qcow2.json
2025/01/23 11:29:26 error: cannot build manifest: no default root filesystem type specified in container, please use "--rootfs" to set manually
error: Recipe `_build-bib` failed with exit code 1

Any idea on how to fix this problem?
Thanks in advance
@tulilirockz tulilirockz linked a pull request Jan 24, 2025 that will close this issue
Open
@SamuelYaron
Copy link
Author

Thanks for the fast work on this issue!

I locally applied the patch from your PR and it resolved this error.

Unfortunately I can still not use the build-* recipes. I now get the following error:

$ just build-vm
+ [[ -n '' ]]
+ [[ 1000 -eq 0 ]]
+ set +e
++ /usr/bin/podman inspect -t image localhost/yourimage:latest
++ jq -r '.[].RepoTags.[0]'
+ resolved_tag=localhost/yourimage:latest
+ return_code=0
+ set -e
+ [[ 0 -eq 0 ]]
++ sudo --askpass /usr/bin/podman images --filter reference=localhost/yourimage:latest --format ''\''{{.ID}}'\'''
+ ID=''\''200c16973652'\''
'\''200c16973652'\'''
+ [[ -z '200c16973652'
'200c16973652' ]]
Cleaning up previous build
[-] Manifest generation step
Message: Generating manifest manifest-qcow2.json
2025/01/24 12:04:48 error: cannot build manifest: initializing dnf in efdedb466e6d50058aa916326c836f7a9ed965fd731553a3775836d2c2c7bf43 container failed: exit status 2
output:
error: unrecognized subcommand 'check'

Usage: yum [OPTIONS] <COMMAND>

For more information, try '--help'.
error: Recipe `_build-bib` failed with exit code 1

@tulilirockz
Copy link
Collaborator

Oh that issue is an issue on the image itself, ublue-os/main does a command called rpm-ostree cliwrap that makes dnf be a symlink to rpm-ostree. For now, bootc-image-builder wont be super happy with that, but you can un-cliwrap it in your custom image if you want to. Its going to work aftwards. Heres an example of how to do it: https://github.com/m2Giles/m2os/blob/4948d5eefd82069479de591c0717141a65929354/remove-cliwrap.sh#L5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: default btrfs filesystem for image ublue-os/image-template
2 participants
@SamuelYaron @tulilirockz