Re: [Astlinux-devel] Can't Add Bind to New Dev Build

[Lonnie A. <li...@lo...>]

> On Feb 20, 2022, at 9:54 AM, Lonnie Abelbeck <li...@lo...> wrote:
> 
> 
>> On Feb 20, 2022, at 9:06 AM, Josh Alberts <jm...@ho...> wrote:
>> 
>> Hello Astlinux Team,
>> 
>> I tried to make a fresh development built last night and I am unable to include 'bind libs and dig tool'. After adding it in 'make menuconfig' this is the error that I get when running the build script:
>> 
>> ...
> 
>> It's not imperative for me to have bind but I like to have it in my dev builds so I can use dig. Would you guys please consider bumping the version of bind to something that will build with Astlinux?
>> 
>> Thanks!
> 
> Hi Josh,
> 
> AstLinux has never included "bind" in the image, the package has originated with an early Buildroot.
> 
> Years ago we looked at adding "dig", but it added a lot to the disk image size ... which 5MB of .xz compressed source might imply.
> 
> Instead the "unbound" package installs unbound-host (with a symlink for "host"), while not "dig" it provides a lot of functionality.  Much better than Busybox's nslookup.
> 
> Lonnie

Josh, another thought...

In cases where it might be handy to have diagnostic tools (like "dig") you can install a Debian LXC container within AstLinux.

LXC container in AstLinux
https://doc.astlinux-project.org/userdoc:guest_lxc_container

The LXC container is not part of the AstLinux image, but uses /mnt/kd/lxc/ for storage, and must be kept updated separately.


Lonnie