GNU bug report logs - #68960
[doc] No host resolution when "Chrooting into an existing system"

Previous Next

Package: guix;

Reported by: Pierre Neidhardt <vabagot <at> disroot.org>

Date: Tue, 6 Feb 2024 20:24:01 UTC

Severity: normal

To reply to this bug, email your comments to 68960 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-guix <at> gnu.org:
bug#68960; Package guix. (Tue, 06 Feb 2024 20:24:01 GMT) Full text and rfc822 format available.
Acknowledgement sent to Pierre Neidhardt <vabagot <at> disroot.org>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Tue, 06 Feb 2024 20:24:01 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Pierre Neidhardt <vabagot <at> disroot.org>
To: bug-guix <at> gnu.org
Subject: [doc] No host resolution when "Chrooting into an existing system"
Date: Tue, 06 Feb 2024 17:21:51 +0100

Following the instructions from the "Chrooting into an existing system"
section of the manual, the resulting chroot fails to resolve hosts, e.g.

--8<---------------cut here---------------start------------->8---
ping gnu.org
--8<---------------cut here---------------end--------------->8---

fails

but

--8<---------------cut here---------------start------------->8---
ping 9.9.9.9
--8<---------------cut here---------------end--------------->8---

works.

This means in particular that most guix commands fail within the chroot
since Guix uses hostnames by default.
This bug report was last modified 87 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.