CPU usage limit to systemd-nspawn container is not working

[gmane@xxxxxxxxxxxxxx (Colin Guthrie)]

patlollamahipal at yahoo.co.in wrote on 18/07/18 21:04:
> *override.conf* is effective when it is placed in
> */etc/systemd/system/systemd-nspawn at service.d/*

I think you missed a . above:
/etc/systemd/system/systemd-nspawn at .service.d/*

> 
> If I have file
> *systemd-nspawn at appscont.service *in */etc/systemd/system.control/systemd-nspawn at appscont.service.d,
> *it is not effective, it's using the template file.

there is no system.control folder.

You should place a file called override.conf (or anything.conf) in a
folder: /etc/systemd/system/systemd-nspawn at appscont.service.d/ if you
want the overrides defined in the .conf file to only apply to that one
machine.

All the best and HTHs

Col


-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/