Hi Joris, Thanks for pointing that out -- it does seem like cfs_quota getting reset is just one of a number of issues we'll encounter with systemd < 218. We don't have any technical barriers in the way of upgrading, and it's something I'd like to see happen, it's just a matter of coordinating with all of the parties involved. MESOS-3425 makes a convincing case for moving ahead with the upgrade, though. :)
On Thu, Apr 21, 2016 at 6:14 PM, Joris Van Remoortere <[email protected]> wrote: > Hey Michael, > > There are a bunch of issues related to running with older versions of > systemd. See MESOS-3425. > > Are you running with systemd disabled? If not, you likely have a category > of other problems mentioned in the ticket to worry about. > > What is preventing you from upgrading the version of systemd? > > Joris > > — > *Joris Van Remoortere* > Mesosphere > > On Fri, Apr 15, 2016 at 6:00 PM, Michael Browning <[email protected]> > wrote: > > > Hi all, > > > > We've run into an interesting issue with Docker and systemd that's > > hampering our attempts to use cfs_quota for CPU isolation with Docker > > containers. The issue is that Docker doesn't tell systemd when it > > changes cpu.cfs_quota_us, so when our Puppet run triggers a `systemctl > > daemon-reload` invocation, the quota is reset to -1. > > > > I assume this could be solved with the `Delegate=true` in the dockerd > unit > > file, but unfortunately we're not running a recent enough version of > > systemd to take advantage. Has anyone else ran into this when using > > DockerContainerizer with cfs_quota, or found a workaround? > > > > Regards, > > Michael > > >
