I made some progress... I modified the script to start the container like this:
exec ${CARCH:+setarch "$CARCH"} systemd-nspawn -q \
-D "$working_dir" \
-E "PATH=/usr/local/sbin:/usr/local/bin:/usr/bin" \
--register=yes --as-pid2 --machine=test \
"${mount_args[@]}" \
"$@"
Now when the scr
Thank you for the reply. I believe the container is being invoked from
a user session. I am unclear how to set the containername. The Arch
tools are invoking systemd-nspawn like this:
exec ${CARCH:+setarch "$CARCH"} systemd-nspawn -q \
-D "$working_dir" \
-E "PATH=/usr/local/sbin:/usr/local/bi
On 11/19/2019 01:19, Andrew Lunn wrote:
> On Mon, Nov 18, 2019 at 11:54:31AM +, Shay Drory wrote:
>> On 11/18/2019 03:29, Andrew Lunn wrote:
>>> On Sun, Nov 17, 2019 at 11:46:15AM +, Shay Drory wrote:
>>>
>>> Hi Shay
>>>
>>> It would be good to Cc: the generic SFP code maintainers.
>> The s
On Fr, 08.11.19 11:15, Philip Withnall (phi...@tecnocode.co.uk) wrote:
> Hello all,
>
> As part of work on a GNOME feature for monitoring how often the user
> uses applications (for example, to let them know that they spent 4
> hours in the Slack app, or 17 hours playing games), I’m trying to work
On Fr, 15.11.19 17:17, John (gray...@archlinux.us) wrote:
> The container is created by one of the Arch Linux build scripts
> (https://git.archlinux.org/devtools.git/tree/arch-nspawn.in). I do
> not believe it runs with its own systemd/dbus. When I am compiling
> (https://git.archlinux.org/devto
