Closed Lophiel closed 2 years ago
I do not have the means to test and set up QubesOS on my end right now. The steps to reproduce the above shown behavior for anyone willing to help out here should be as follows:
docker build -f .dockerfile_base -t "like_dbg_base" --build-arg USER=user .
docker build -f .dockerfile_rootfs -t "like_rootfs" --build-arg USER=user .
docker run --privileged --rm -it -v "$(pwd)/io":/io like_rootfs /bin/bash
./home/user/rootfs.sh -n "filesystem" -a x86_64 -d bullseye -u user
Note: I left out the -p [package list]
argument for the root.sh
script for brevity reasons. One could add the list as defined in config.ini
.
The root cause of the error is not yet clear to me, but it seems that the location (/io/rootfs
), in which debootstrap
attempts to install the rootfs has not enough permissions. I do not know QubesOS well enough to blindly ship a fix and without a working test-bench I cannot fix this.
I happily take a PR that fixes things on QubesOS, which I can then test again Debian/Fedora/Arch to ensure nothing breaks on those ends.
The testing for this has become a lot easier and faster with the latest additions to the main branch!
You can now invoke ./start_kgdb.py -v --partial 4
to only run stage 4, which builds the root filesystem.
So we're able to skip the whole kernel building phase.
@Zophike1 If you want to take another crack at it feel free to do so.
My best bet is still on the containers permissions.
Maybe playing around with the cap_add
flag may help.
References:
Closing this for now as there seems no activity here. Personally, I'd consider QubeOS support as optional.
Describe the bug Building like-dbg throws the error "Failed to run RootFSBuilder"
To Reproduce Steps to reproduce the behavior:
Expected behavior To actually run RootFSBuilder and extract the RootFS to build like-dbg's docker images.
Screenshots
Desktop (please complete the following information): Fill me in on the specs of your environment:
Additional context Important note is that i'm running ./start-kdbg.py in a non-ctf context! without any additional flags. Docker can pull and build images just fine but the issue occurs when I run the aforementioned script.