On Sun, Nov 23, 2014 at 02:40:29AM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> On Sun, Nov 23, 2014 at 12:14:32AM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> > On Sat, Nov 22, 2014 at 02:47:49PM +0100, David Herrmann wrote:
> > > Hi
> > >
> > > On Fri, Nov 21, 2014 at 5:00 AM, Peter Hutterer
> > >
On Sun, Nov 23, 2014 at 12:14:32AM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> On Sat, Nov 22, 2014 at 02:47:49PM +0100, David Herrmann wrote:
> > Hi
> >
> > On Fri, Nov 21, 2014 at 5:00 AM, Peter Hutterer
> > wrote:
> > > I was playing around with systemd-nspawn and systemd-run. The latter
> >
On Sat, Nov 22, 2014 at 02:47:49PM +0100, David Herrmann wrote:
> Hi
>
> On Fri, Nov 21, 2014 at 5:00 AM, Peter Hutterer
> wrote:
> > I was playing around with systemd-nspawn and systemd-run. The latter doesn't
> > seem to let me run a command that solely exists on the container.
> > simple way o
Hi
On Fri, Nov 21, 2014 at 5:00 AM, Peter Hutterer
wrote:
> I was playing around with systemd-nspawn and systemd-run. The latter doesn't
> seem to let me run a command that solely exists on the container.
> simple way of reproducing: drop a file foo into the container, then on the
> host run
>
>
I was playing around with systemd-nspawn and systemd-run. The latter doesn't
seem to let me run a command that solely exists on the container.
simple way of reproducing: drop a file foo into the container, then on the
host run
systemd-run -M mycontainer /path/to/foo
I expected this to run fo
