On Wed, Oct 04, 2017 at 05:02:27PM +0200, Kees Bos wrote:
> On wo, 2017-10-04 at 09:35 -0500, Serge E. Hallyn wrote:
> > Quoting Kees Bos (cornelis@gmail.com):
> > >
> > > I'm not using it, but do expect the extra args:
> > >
> > > while [ {{ '${#@}' }} -gt 3 ] ; do
> > > ...
> > > shif
agreed to both, lxc-update-config should delete it, and it should be
(initially the only) member of a (new) group of keys to ignore, bc
it cannot possibly hurt. Do you happen to have time to write one
or both patches?
thanks,
-serge
On Wed, Oct 04, 2017 at 03:35:08PM -0400, Adrian Pepper wrote:
Does mentioning lxc.pivotdir really need to be a fatal error? Currently
it seems fatal to the degree that "lxc-ls -f" does not show the
container at all, not RUNNING and not STOPPED.
Or, at least, could the lxc-update-config command be modified to
effectively delete mentions of lxc.pivotdir?
(Com
* Tomasz Chmielewski [2017-04-16 02:32]:
> When there are other iptables rules applied on the system with
> iptables-persistent [...] - this will basically
> wipe the rules which LXD applies on startup.
>
> What's the recommended approach to deal with it?
Very good question. I've hit by the same
Hi,
I've been using ubuntu 16.04 and LXC 2.08 and checkpointing with CRIU 3.4,
I've recently tried upgrading my setup to LXC 2.1 and since checkpointing
fails.
I see there are commits that include verifying the version of CRIU in 2.1
-- is this the problem or is there something else I'm missing?
On wo, 2017-10-04 at 09:35 -0500, Serge E. Hallyn wrote:
> Quoting Kees Bos (cornelis@gmail.com):
> >
> > I'm not using it, but do expect the extra args:
> >
> > while [ {{ '${#@}' }} -gt 3 ] ; do
> > ...
> > shift
> > done
> >
> > It might be that some users will need the last extra a
Quoting Kees Bos (cornelis@gmail.com):
> I'm not using it, but do expect the extra args:
>
> while [ {{ '${#@}' }} -gt 3 ] ; do
> ...
> shift
> done
>
> It might be that some users will need the last extra argument (stage:
> pre-start|start|post-stop). This is currently not available in
I'm not using it, but do expect the extra args:
while [ {{ '${#@}' }} -gt 3 ] ; do
...
shift
done
It might be that some users will need the last extra argument (stage:
pre-start|start|post-stop). This is currently not available in the
environment.
I can live without these extra arguments,
