pkg chroot issues?

bapt at bapt at
Sun May 22 20:32:49 UTC 2016

On Sun, May 22, 2016 at 10:31:08PM +0200, bapt at wrote:
> On Sun, May 22, 2016 at 01:24:12PM -0700, Tim Kientzle wrote:
> > Crochet has some experimental hooks to install packages onto the system being built, but this seems to be hitting problems due to limitations in 'pkg -c'.  In particular, it seems that pkg performs the chroot before it does any network lookups.  This is a problem if the chroot is not a complete system environment (which it cannot be when you're building an image for another system).
> > 
> > There's some further discussion on github:
> > 
> >
> > 
> > Any suggestions?
> > 
> I'll reply directly to github thanks for pointing me to the ticket
> Best regards,
> Bapt

As people might only follow this thread and not the ticket here is what I

pkg supports an option for that which is pkg -o NAMESERVER= to avoid having to
copy resolv.conf it was broken in 1.8 but I fixed it in pkg 1.8.0 which has been
released today.

the problem with pkg -c is that it calls chroot very early. To avoid that
problem we have added pkg -r which does not perform any chroot at all therefore
having not network issue, but the ports tree are is not yet entirely aware of it
and some scripts (preinstall/postinstall) might cause some issues.
at least creating users from the script is safe in that regard. for most simple
case that should work.

Best regards,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <>

More information about the freebsd-current mailing list