Containerized libguestfs including virt-customize, guestfish, etc.
- Runs as non-root user
- Multi-platform image
- Helper scripts
guestfishManipulate a virtual machine / image using the guest filesystem shellvirt-builderBuild virtual machine images quickly
virt-customizeCustomize a virtual machine / image
piBoot a virtual machine / image using a dockerized ARM emulator that emulates a Raspberry Pi
copy-outCopy files out of a virtual machine / image
git clone https://github.com/bkahlert/libguestfs.git
cd libguestfs
# Build image and output to docker (default)
docker buildx bake
# Build multi-platform image
docker buildx bake image-all- Docker Hub
bkahlert/libguestfs - GitHub Container Registry
ghcr.io/bkahlert/libguestfs
Following platforms for this image are available:
- linux/amd64
- linux/arm/v7
- linux/arm64/v8
- linux/ppc64le
- linux/riscv64
- linux/s390x
docker run -it --rm \
-v "$PWD":"$PWD" \
-w "$PWD" \
bkahlert/libguestfs:edge \
guestfish
><fs> add disk.img format:raw
><fs> launch
><fs> mount /dev/sda ./
><fs> ls /
><fs> copy-out /boot data
><fs> umount-all
><fs> exitdocker run -i --rm \
-v "$PWD":"$PWD" \
-w "$PWD" \
bkahlert/libguestfs:edge \
guestfish \
--ro \
--add disk.img format:raw \
--mount /dev/sda:/ \
<<COMMANDS
ls /
-copy-out /boot ./
umount-all
exit
COMMANDSThe command requires disk.img in this directory, mounts it with the guestfish tool and executes all guestfish commands enclosed by COMMANDS on the
mounted disk.img.
In this case the directory /boot and its contents is copied to the current working directory.
💡 Did you notice the leading dash in front of the
copy-outcommand? Running guestfish non-interactively the first command that gives an error causes the whole shell to exit. By prefixing a command with-guestfish will not exit if an error is encountered.
💡 If you prefix a command with
!(e.g.!id) the command will run on the host instead of the mounted guest. Since the libguestfs tools are containerized themselves, "host" signifies the containerized libguestfs hosting Ubuntu installation — and not you actual OS.
This image can be configured using the following options of which all but APP_USER and APP_GROUP exist as both—build argument and environment variable.
You should go for build arguments if you want to set custom defaults you don't intend to change (often). Environment variables will overrule any existing
configuration on each container start.
APP_USERName of the main user (default:libguestfs)APP_GROUPName of the main user's group (default:libguestfs)DEBUGWhether to log debug information (default:0)TZTimezone the container runs in (default:UTC)LANGLanguage/locale to use (default:C.UTF-8)PUIDUser ID of thelibguestfsuser (default:1000)PGIDGroup ID of thelibguestfsgroup (default:1000)LIBGUESTFS_DEBUGSet this to 1 in order to enable massive amounts of debug messages. If you think there is some problem inside the libguestfs appliance, then you should use this option. (default:0)LIBGUESTFS_TRACESet this to 1 and libguestfs will print out each command / API call in a format which is similar to guestfish commands. (default:0)
# Build single image with build argument TZ
docker buildx bake --set "*.args.TZ=$(date +"%Z")"
# Build multi-platform image with build argument TZ
docker buildx bake image-all --set "*.args.TZ=$(date +"%Z")"
# Start container with environment variable TZ
docker run --rm \
-e TZ="$(date +"%Z")" \
-v "$(pwd):$(pwd)" \
-w "$(pwd)" \
libguestfs:localgit clone https://github.com/bkahlert/libguestfs.git
cd libguestfs
# Use Bats wrapper to run tests
curl -LfsS https://git.io/batsw |
DOCKER_BAKE="--set '*.tags=test'" bash -s -- --batsw:-e --batsw:BUILD_TAG=test testBats Wrapper is a self-contained wrapper to run tests based on the Bash testing framework Bats.
💡 To accelerate testing, the Bats Wrapper checks if any test is prefixed with a capital X and if so, only runs those tests.
If you run into problems, try running your intended steps interactively with verbose logging turned on:
docker run -it --rm \
-e "LIBGUESTFS_DEBUG=1" \
-e "LIBGUESTFS_TRACE=1" \
-v "$PWD":"$PWD" \
-w "$PWD" \
bkahlert/libguestfs:edge \
guestfishTo debug the image the following lines might become handy:
# build local image with specified tag
docker buildx bake --set '*.tags=test'
# copy something to test with
cp test/fixtures/tinycore.iso disk.img
# start container interactively with a bash
docker run \
-e LIBGUESTFS_DEBUG=1 \
-e LIBGUESTFS_TRACE=1 \
-e DEBUG=1 \
-e TZ=CET \
-e PUID=68039910 \
-e PGID=584555228 \
-e TERM=xterm-256color \
-v /var/run/docker.sock:/var/run/docker.sock \
-v "$PWD":"$PWD" \
-w "$PWD" \
--interactive \
--tty \
--rm \
--entrypoint /bin/bash \
--name libguestfs-test \
test
# fixes (normally performed by entrypoint.sh)
chmod 0644 /boot/vmlinuz*
usermod -a -G kvm "$(whoami)"
# run guestfish interactively
guestfish
# or as root: (see entrypoint_user.sh for details)
LIBGUESTFS_BACKEND=direct guestfish
# run guestfish using the original entrypoint
entrypoint.sh guestfish \
--ro \
--add disk.img format:raw \
--mount /dev/sda:/ \
<<COMMANDS
ls /
-copy-out /boot ./
umount-all
exit
COMMANDS Want to contribute? Awesome! The most basic way to show your support is to star the project, or to raise issues. You can also support this project by making a PayPal donation to ensure this journey continues indefinitely!
Thanks again for your support, it's much appreciated! 🙏
MIT. See LICENSE for more details.