[CRIU] Configuration file /etc/criu.d

Adrian Reber adrian at lisas.de
Thu Oct 27 09:02:25 PDT 2016


On Mon, Oct 24, 2016 at 02:24:26PM +0300, Pavel Emelyanov wrote:
> Looping in Adrian who's been looking at this for some time a while ago.

I saw the need for something like this and was hoping to motivate
someone else to implement this ;-)

I will have a look how this can be done. This would probably be
something which could be discussed at the Linux Plumbers Conference.

		Adrian

> On 10/22/2016 03:24 AM, Barve, Yogesh Damodar wrote:
> > I would like to continue the discussion for having a configuration file to specify default parameters from which CRIU can load during execution.
> > The need for such option has also been discussed earlier here: https://lists.openvz.org/pipermail/criu/2016-August/030819.html
> > 
> > I am trying to use the CRIU-docker to C/R a container, and stumbled into the issue of hitting the default --ghosh-limit. Now to resolve this issue, I have to pass ghost-limit configuration
> > parameter to CRIU, but there is no current option in Docker CLI to accomplish this. 
> > 
> > I am referring to this issue on:
> > 
> > https://github.com/xemul/criu/issues/230
> > 
> > So if there was a way to specify custom config in a config file from which the criu could read, then this issue could be easily solved. I am sure there will be other such use cases wherein there will be a need to set the configuration options.
> > 
> > So could we have such feature support in CRIU to specify custom options?
> > 
> > thanks,
> > Yogesh
> > _______________________________________________
> > CRIU mailing list
> > CRIU at openvz.org
> > https://lists.openvz.org/mailman/listinfo/criu
> > .
> > 


More information about the CRIU mailing list