Closed morbitzer closed 2 years ago
Vincinator
commented
2 years ago Hi @morbitzer, thanks for the issue description.
I could not reproduce the issue on my test machine. I tested with commit caa5163b (current latest commit in main branch).
Could you also attach the full build log? A log file should be available in the <repo>/.build/ folder. I think make kvm-dev > debug.log 2>&1 should also be fine.
Thanks, Vincent
gyptazy
commented
2 years ago Hey @morbitzer,
thanks for creating an issue. Unfortunately, I was unable to reproduce this issue as well as @Vincinator already mentioned. Beside this, our GitHub pipeline doesn't encounter any issues here (based on the last merged commit). However, you might debug this by setting set -x in build.sh, bin/garden-build, bin/garden-chroot, bin/garden-init (and other files that are invoked during build and changed by you).
Unfortunately, I couldn't find any branch from you. If it's ok for you, you might share (push) it so we may have a look. But it's weird that you still have issues on a fresh repo clone.
Edit: Just saw you're using docker, instead of Podman. Unfortunately I was also unable to reproduce this with docker as CRE. Maybe you could just give it a new try with Podman. When building with docker - is export GARDENLINUX_BUILD_CRE=docker set? Is your git checkout located on a shared volume or getting shared to any other tools like Vagrant etc.? I think defining set -x could lead to the fastest solution to find the issue.
Regards, gyptazy
morbitzer
commented
2 years ago It turned out that I was accidentally not working on the latest commit - I was using commit 118d3b65666dd18e7d01a2a9f0b2d45d4de46862. While this commit worked for me 2 weeks ago, and now doesn't anymore - I suspect a system update to be the reason for this, but I'm not sure. Commit 3f532ab2e984696b4b77cec184efc63d046a4b03 didn't fix the issue, so it seems to be a different issue related to system-updates as is #1014.
However, the good news is that using the latest commit (f111b51fb243f9e41d8e1dcfe6b2f2b862135f33), the error is gone. Using git bisect, I was able to figure out that ca5ef159fbf27e02181f54e539452c45b8849e9e fixes the error. Yet, as this is a quite large commit and the error is resolved, I didn’t dive into what exactly fixed it.
Sorry for the inconvenience, I thought I was working on an up-to-date version, but well, I didn't.
Btw, @gyptazy I learned that adding set -x to /bin/garden-chroot doesn't seem to be a good idea. The output of the script is used by other scripts such as bin/garden-slimify, so set -x will break these. So for everyone coming here due to searching the error xargs: unmatched single quote; by default quotes are special to xargs unless you use the -0 option, remove the set -x from /bin/garden-chroot.
What happened:
make kvm-devfails withmake: *** [Makefile:138: kvm-dev] Error 1. The createdrootfs.rawis not copied out of the container.What you expected to happen:
No Error.
How to reproduce it (as minimally and precisely as possible):
Pull repo and execute
make kvm-devAnything else we need to know:
Earlier, I was trying to add a new feature. While this worked two weeks ago, it now fails with an
Error 1, and the error now also happens when I execute themake kvm-devin a new, unmodified clone of repo. I tried to delete all docker images, but that didn't help.Adding
apparmor=1 security=apparmorto the kernel command line, as described in https://github.com/gardenlinux/gardenlinux/blob/main/docs/build/troubleshooting.md did not help either.I did apply PR #1015, hoping it would fix the problem, but the error occurs with and without it.
Unfortunately, I am not able to determine what exactly causes the error. I tried to build with
--debug, but also that does not result in any further information. When using the--manualflag, the build seems to work, and the error only occurs when exciting the container.Environment: