From: Thorsten Wilms <t_w_@freenet.de>
To: guix-devel@gnu.org
Subject: Re: Chrooting into GuixSD
Date: Wed, 13 Jun 2018 12:09:13 +0200 [thread overview]
Message-ID: <df9dcbd1-094e-2a95-ccc2-0a2f620e696a@freenet.de> (raw)
In-Reply-To: <20180613081346.jhkzdorwjp6albqx@abyayala>
On 13.06.2018 10:13, Nils Gillmann wrote:
>>> Is this ability to chroot into GuixSD worth mentioning in the manual?
>> IMHO it is not worth to be mentioned in the manual, as it is the same as
>> for all Linux systems.
> Not really, since you can not*fully* chroot a GuixSD. Some functions
> will not work, like interacting with the daemon or what it was. Last
> time I tried this was at least 1.5 years ago.
You can interact with the daemon:
cd /path/to/guix/root
sudo mount --bind /dev dev
sudo mount --bind /proc proc
sudo mount --bind /sys sys
sudo unshare -m sudo chroot . /run/current-system/profile/bin/bash
source /etc/profile
guix-daemon --build-users-group=guixbuild &
If you then `su` to a plain user, do `source /etc/profile` again.
I think all of `guix pull`. `reconfigure` and `package` search, install
and update worked here with that approach. `guix download` failed due to
nss certificates, until I added:
export SSL_CERT_DIR="$HOME/.guix-profile/etc/ssl/certs"
export
SSL_CERT_FILE="$HOME/.guix-profile/etc/ssl/certs/ca-certificates.crt"
export GIT_SSL_CAINFO="$SSL_CERT_FILE"
--
Thorsten Wilms
thorwil's design for free software:
http://thorwil.wordpress.com/
next prev parent reply other threads:[~2018-06-13 10:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 4:04 Chrooting into GuixSD swedebugia
2018-06-13 7:13 ` Hartmut Goebel
2018-06-13 8:13 ` Nils Gillmann
2018-06-13 10:09 ` Thorsten Wilms [this message]
2018-06-14 12:18 ` Nils Gillmann
2018-06-14 13:04 ` Ricardo Wurmus
2018-06-14 14:29 ` Oleg Pykhalov
2018-06-14 15:01 ` Ricardo Wurmus
2018-06-15 10:21 ` swedebugia
2018-07-05 8:55 ` Chris Marusich
2018-06-15 15:01 ` Ludovic Courtès
2018-06-15 18:20 ` Thorsten Wilms
2018-06-16 15:43 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=df9dcbd1-094e-2a95-ccc2-0a2f620e696a@freenet.de \
--to=t_w_@freenet.de \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).