From: jgart <jgart@dismail.de>
To: help-guix@gnu.org
Subject: Running make inside a Guix Container From Outside
Date: Mon, 6 Sep 2021 12:57:32 -0400 [thread overview]
Message-ID: <20210906125732.GB27512@gac.attlocal.net> (raw)
Hi Guixers,
I started making a quick bash script that started like this:
```
#!/bin/sh
git clone https://git.savannah.gnu.org/git/guix.git guix-3000
cd guix-3000
guix environment guix --container
./bootstrap
./configure --local-statedir=/var
time make
exit
print "ready for hacking"
```
One of the problems with the above script is that the `guix environment guix --container` blocks `./bootstrap` etc...
I'm thinking of rewriting the script in python or guile using some form of async to solve that issue if needed.
Once `guix environment guix --container` is unblocked by me killing the process manually,
the following commands run outside the container and fail. This is expected.
So, I ran `guix environment guix --container` in one terminal and opened another terminal to see if I can
first test running commands in containers from the "outside" with `guix container exec`.
I tried `guix container exec PID "./boostrap"` and it didn't fail. In the other terminal running the
container I looked to see if there was any change to container's directory structure and there was none.
I also ran `guix container exec PID "./configure --localstatedir=/var"` and
`guix container exec PID "time make"`.
Am I misusing `guix container exec`?
Is it currently possible to run arbitrary commands in guix containers from outside guix containers?
all best,
_________________________________________
/ 3B1D 7F19 E36B B60C 0F5B 2CA9 A52A A2B4 \
\ 77B6 DD35 /
-----------------------------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
next reply other threads:[~2021-09-06 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 16:57 jgart [this message]
2021-09-07 15:47 ` Running make inside a Guix Container From Outside zimoun
2021-09-10 5:24 ` jgart
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=20210906125732.GB27512@gac.attlocal.net \
--to=jgart@dismail.de \
--cc=help-guix@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.
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).