From nobody Thu Apr 16 12:44:54 2026 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4fxHm22Y8xz6ZbYk; Thu, 16 Apr 2026 12:45:06 +0000 (UTC) (envelope-from vermaden@interia.pl) Received: from smtpo49.interia.pl (smtpo49.interia.pl [217.74.67.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4fxHm16xFTz3rHt; Thu, 16 Apr 2026 12:45:05 +0000 (UTC) (envelope-from vermaden@interia.pl) Authentication-Results: mx1.freebsd.org; none Date: Thu, 16 Apr 2026 14:44:54 +0200 From: vermaden Subject: Re: Building VM-IMAGE(s) from Source To: David Chisnall Cc: "freebsd-stable@FreeBSD.org" , "freebsd-hackers@FreeBSD.org" , "freebsd-current@freebsd.org" X-Mailer: interia.pl/pf09 In-Reply-To: References: X-Originating-IP: 45.148.42.24 Message-Id: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interia.pl; s=dk; t=1776343497; bh=hak5z+L3osPgZ9xJl9bCFbjvWRxIeONDgw22Uf8zO6c=; h=Date:From:Subject:To:Message-Id:MIME-Version:Content-Type; b=ULDhTzRrKfvjXmTVhYIAA75TFNnfhcym/pOgBkaLf0ePXPi4h7XbdMdgKsH+//jEt 3V9nyvL758OqntJkKPVJvilfAEclTzLE27Z9x9aPcP7mRK3CZMopE7P5FU0NAsQ9xt JqKzPGvNnly3aY57FeHGQRpxGry4jTQIgzWDl4vo= X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16138, ipnet:217.74.64.0/22, country:PL] X-Rspamd-Queue-Id: 4fxHm16xFTz3rHt X-Spamd-Bar: ---- Yes and no. For a start - I do not see options for PKGBASE in the poudriere-image(8) man page ... so I am not sure if I end up with PKGBASE system (probably not) or classic Distribution Sets system - but that can (can?) be probably configured some undocumented way. I already have a system that builds packages - so 3rd party packages are ready in some repo. I also already have a system that builds PKGBASE repo - so PKGBASE packages are ready. So when I will try to use poudriere-image(8) instead of verimg(8) I would have these downgrades: - I need to build PKGBASE FreeBSD 'Base System' everytime from source (which I do not need/want). - I need to build 3rd party pkg(8) packages from FreeBSD Ports (which I do not need/want). - I can not create custom/additional ZFS datasets and custom ZFS filesystem sizes. - I can not create additional FAT32 filesystems with configs for cloud-init(1) use. - I am not sure if poudriere-image(8) supports geli(8) - which I also sometimes need in images - and I plan to add geli(8) support to verimg(8) ... and I doubt it will be added to poudriere-image(8) anytime soon. With verimg(8) I just use PKGBASE packages as 'Base System' from repo I previously built and then add 3rd party pkg(8) packages from other repo that I already built. That way I 'suffer' once and then I can build various images in minutes/seconds - not in long hours compiling everything each time. One can also as a question ... why FreeBSD as a project maintains 3 different 'building systems'? 1. We have 'classic' # make buildworld buildkernel update-packages at /usr/src dir. 2. We have 'release.sh' inside /usr/src/release dir. 3. We have poudriere-image(8) for similar purposes. 4. We also have mkimg(8) which is used by both 'release.sh' and poudriere-image(8) tools. But as they exists ... so I can only assume that they all are needed. Regards, vermaden Temat: Re: Building VM-IMAGE(s) from Source Data: 2026-04-16 12:29 Nadawca: "David Chisnall" Adresat: "vermaden" ; DW: "freebsd-stable@FreeBSD.org" ; "freebsd-hackers@FreeBSD.org" ; "freebsd-current@freebsd.org" ; > For every other use case, `poudriere image` is a far more flexible > tool (does custom builds, can do base-system overlays, install > packages, build packages from ports-tree overlays, and so on), > so why would you write a tool that does a small subset of what > it does? > > David