Another followup suggests my suggestions (at least regarding
lxc-update-config itself) have been covered.
I will try to investigate the script and those changes since it is
something which can be done without knowledge of actual lxc internals.
While we use containers heavily in our department, muc
On do, 2017-10-05 at 10:27 +0200, Christian Brauner wrote:
> On Wed, Oct 04, 2017 at 09:35:25AM -0500, Serge Hallyn wrote:
> >
> > Quoting Kees Bos (cornelis@gmail.com):
> > >
> > > I'm not using it, but do expect the extra args:
> > >
> > > while [ {{ '${#@}' }} -gt 3 ] ; do
> > > ...
>
On Wed, Oct 04, 2017 at 09:35:25AM -0500, Serge 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
On Wed, Oct 04, 2017 at 06:53:16PM -0500, Serge Hallyn wrote:
> 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
I sent a branch [1] that does:
- removes lxc.kmsg and lxc.pivotdir from config files if deteced
