distrobuilder icon indicating copy to clipboard operation
distrobuilder copied to clipboard

Distrobuilder Release is Old

Open brandonkal opened this issue 1 year ago • 3 comments

I used the distrobuilder 3.0 release but found DISTROBUILDER_ROOT_UUID doesn't work. Please cut a new release

brandonkal avatar Jun 29 '24 06:06 brandonkal

Change sed -i "s#root=[^ ]*#root=${DISTROBUILDER_ROOT_UUID}#g" /boot/grub/grub.cfg to sed -i "s#root=[^ ]*#root=/dev/sda2#g" /boot/grub/grub.cfg in your debian.yaml

nobodyman1 avatar Aug 26 '24 08:08 nobodyman1

I mean I got it working by building distrobuilder myself. But the released version is older than what is being used by the images builder CI.

brandonkal avatar Aug 27 '24 12:08 brandonkal

If you normally use distrobuilder through Snap you can just use latest/edge channel which will use the latest version on git. This way you don't have to wait for release.

foxtrotcz avatar Oct 02 '24 19:10 foxtrotcz

This issue popped up on the the forums today.

Could we consider making a new release? It would also be great if we could build binaries like we do with the LXC projects.

Then I could ask the person to try the binary from the release page. That would work even if the person does not use Snap packages.

jarrodu avatar Oct 23 '24 12:10 jarrodu

We can do a new release, but we can't provide static binaries for distrobuilder as it actively relies on CGO.

stgraber avatar Oct 23 '24 15:10 stgraber

Wouldnt this just mean the binary is dynamically linked to glibc (in case od Debian) which is available in most distros either way?

foxtrotcz avatar Oct 23 '24 19:10 foxtrotcz

Doesn't quite work that way, it would get linked to the current version of eglibc on the system that built it, trying to run the binary on a system running an older version of eglibc would then fail with a linker error.

That's why you usually don't distribute dynamically linked binaries.

stgraber avatar Oct 23 '24 20:10 stgraber

Oh, thanks for explanation.

foxtrotcz avatar Oct 23 '24 20:10 foxtrotcz