unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Efraim Flashner <efraim@flashner.co.il>,
	"Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Running eolie in a container (was: bug#46532: plantuml in pure environment…)
Date: Fri, 26 Feb 2021 22:53:54 +0100	[thread overview]
Message-ID: <868s7a1onh.fsf@gmail.com> (raw)
In-Reply-To: <YCuRKQTv/GhzfIUo@3900XT>

Hi Efraim,

On Tue, 16 Feb 2021 at 11:32, Efraim Flashner <efraim@flashner.co.il> wrote:

> I have the following scriptlet that someone shared for running eolie in
> a container. I'm guessing it could be modified to run platuml if needed.

> guix environment \
> --preserve='^DISPLAY$' --container --network \
> --expose=/etc/machine-id \
> --expose=/etc/ssl/certs/ \
> --share=$HOME/.local/share/eolie/=$HOME/.local/share/eolie/ \
> --share=/tmp/.X11-unix/=/tmp/.X11-unix/ \
> --share=$HOME/.Xauthority=$HOME/.Xauthority \
> --ad-hoc eolie nss-certs dbus --  eolie

From the manual [1],

--8<---------------cut here---------------start------------->8---
guix environment --preserve='^DISPLAY$' --container --network \
  --expose=/etc/machine-id \
  --expose=/etc/ssl/certs/ \
  --share=$HOME/.local/share/eolie/=$HOME/.local/share/eolie/ \
  --ad-hoc eolie nss-certs dbus --  eolie
--8<---------------cut here---------------end--------------->8---

is it not enough for eolie?  Is the 2 lines

   --share=/tmp/.X11-unix/=/tmp/.X11-unix/ \
   --share=$HOME/.Xauthority=$HOME/.Xauthority \

really required?  If yes, the manual should be updated. :-)

1: <https://guix.gnu.org/manual/devel/en/guix.html#Invoking-guix-environment>


All the best,
simon


           reply	other threads:[~2021-02-26 21:56 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <YCuRKQTv/GhzfIUo@3900XT>]

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=868s7a1onh.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=arne_bab@web.de \
    --cc=efraim@flashner.co.il \
    --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).