kubevirt.github.io
kubevirt.github.io copied to clipboard
kubevirt
make build failed
Made some page and blog updates for KubeVirt Summit and wanted to check the local build. unfortunately it failed out.
To repeat:
- $ export SELINUX_ENABLED=true
- ran
make build_img -
make build
Output: Makefile: Build jekyll site scripts/update_changelog.sh Cloning into 'build/kubevirt'... remote: Enumerating objects: 245431, done. remote: Counting objects: 100% (181/181), done. remote: Compressing objects: 100% (117/117), done. remote: Total 245431 (delta 84), reused 120 (delta 63), pack-reused 245250 Receiving objects: 100% (245431/245431), 266.44 MiB | 4.50 MiB/s, done. Resolving deltas: 100% (168708/168708), done. Already on 'main' Your branch is up to date with 'origin/main'. Already up to date. egrep: warning: egrep is obsolescent; using grep -E egrep: warning: egrep is obsolescent; using grep -E egrep: warning: egrep is obsolescent; using grep -E ... egrep: warning: egrep is obsolescent; using grep -E egrep: warning: egrep is obsolescent; using grep -E egrep: warning: egrep is obsolescent; using grep -E rake make: rake: No such file or directory make: *** [Makefile:105: build] Error 127
I have not looked further into it.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kubevirt-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.