I tried to reproduce in a freshly installed and fully updated xenial vm
(admittedly not a desktop installation). Starting docker containers with
the --kernel-memory argument works fine, and the value in
/sys/fs/cgroup/memory/memory.kmem.limit_in_bytes is as expected. I get
the EBUSY error writing to /sys/fs/cgroup/memory/system.slice/lxc-
net.service/memory.kmem.limit_in_bytes, but I strongly suspect this is
unrelated.

My kernel is:

$ uname -a
Linux lp1568592 4.4.0-18-generic #34-Ubuntu SMP Wed Apr 6 14:01:02 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

Can you update, then see if your docker problem remains? If so, does it
work without the --kernel-memory argument? Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568592

Title:
  bug of "memory.kmem.limit_in_bytes" and "memory.kmem.usage_in_bytes"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568592/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to