On Tue, 25.08.15 10:09, Kai Hendry (hen...@webconverger.com) wrote:
On Mon, 24 Aug 2015, at 08:05 PM, Lennart Poettering wrote:
I'd be careful with things like this... You invoke firefox as PID 1
then. On UNIX PID 1 is special, it needs to reap foreign children and
needs to handle signals
On Sun, 23.08.15 21:58, Kai Hendry (hen...@webconverger.com) wrote:
Hi there,
I've managed to get Firefox running like so:
sudo systemd-nspawn --setenv=DISPLAY=:0 \
--setenv=XAUTHORITY=~/.Xauthority \
--bind-ro=$HOME/.Xauthority:/root/.Xauthority \
On Mon, 24 Aug 2015, at 08:05 PM, Lennart Poettering wrote:
I'd be careful with things like this... You invoke firefox as PID 1
then. On UNIX PID 1 is special, it needs to reap foreign children and
needs to handle signals differently, thus taking arbitrary processes
and running them like this
Hi there,
I've managed to get Firefox running like so:
sudo systemd-nspawn --setenv=DISPLAY=:0 \
--setenv=XAUTHORITY=~/.Xauthority \
--bind-ro=$HOME/.Xauthority:/root/.Xauthority \
-D ~/containers/firefox \
firefox
However I want to
On 08/23/2015 07:17 AM, Kai Hendry wrote:
On Sun, 23 Aug 2015, at 10:05 PM, Mantas Mikulėnas wrote:
Try adding --bind=/tmp/.X11-unix, for the named X11 sockets.
Ah! Thank you Mantas. I logged this tip on http://dabase.com/e/12009/
Note that this allows the containerized app to punch through
On Sun, Aug 23, 2015 at 4:58 PM, Kai Hendry hen...@webconverger.com wrote:
Hi there,
I've managed to get Firefox running like so:
sudo systemd-nspawn --setenv=DISPLAY=:0 \
--setenv=XAUTHORITY=~/.Xauthority \
--bind-ro=$HOME/.Xauthority:/root/.Xauthority \
On Sun, 23 Aug 2015, at 10:05 PM, Mantas Mikulėnas wrote:
Try adding --bind=/tmp/.X11-unix, for the named X11 sockets.
Ah! Thank you Mantas. I logged this tip on http://dabase.com/e/12009/
___
systemd-devel mailing list
