Just a fresh installation from "http://cdimage.ubuntu.com/daily-
live/current/xenial-desktop-amd64.iso" will definitly have this issue,
not my PC's problem.
After installing "http://cdimage.ubuntu.com/daily-live/current/xenial-
desktop-amd64.iso",
# echo 10 > /sys/fs/cgroup/memory/system.
This bug is critical because docker 1.10 will crash when running "docker
run --kernel-memory 1G ubuntu bash"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1568592
Title:
bug of "memory.
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 t
Btw attaching logs does more than identify your hardware, it attaches a
lot of logs from the system. If you still have the problem after
updating, please do go ahead and run the apport-collect command from
comment #2.
--
You received this bug notification because you are a member of Kernel
Packag
Hi, after full upgrade, "memory.kmem.limit_in_bytes" and
"memory.kmem.usage_in_bytes" works not after executing docker with
"--kernel-memory" argument.
--
But if you run a command like "docker run -it --rm ubuntu bash" without
--kernel-memory argument,
are you able to get the correct value of "c
Sorry, "not after executing docker with" should be "only after executing
docker with"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1568592
Title:
bug of "memory.kmem.limit_in_bytes" an
Thanks, but a strange thing is that lxc performs different from docker.
Can you try the following?
# sudo -i
# lxc-start -n ubuntu1
# echo 1g > /sys/fs/cgroup/memory/lxc/ubuntu1/memory.limit_in_bytes
# echo 1g > /sys/fs/cgroup/memory/lxc/ubuntu1/memory.memsw.limit_in_bytes
# lxc-freeze -n ubuntu1
Previously, I am always thinking the following:
1) memory.usage_in_bytes = memory.kmem.usage_in_bytes + "Non-Kernel
Memory Data"
2) the data of "memory.kmem.usage_in_bytes" cannot be moved to swap
which indicates that memory.usage_in_bytes should be always >0 since
memory.kmem.usage_in_bytes sho
So I think there is still bug about memory.kmem.limit_in_bytes.
If I don't limit the kmem of lxc container at the beginning,
"memory.limit_in_bytes" can be set to zero by the above step.
If I limit the kmem of lxc container at the beginning,
"memory.limit_in_bytes" cannot be set to zero, also b
The behavior seems odd on the face of it, but I'm not an expert on the
memory controller cgroup implementation. Our implementation is the same
as in upstream Linux, so if you feel there are problems then it's
probably best to raise these with the upstream developers directly. If
they make changes t
On Mon, Apr 11, 2016 at 03:44:37PM -, Cui Wei wrote:
> Hi, after full upgrade, "memory.kmem.limit_in_bytes" and
> "memory.kmem.usage_in_bytes" works not after executing docker with
> "--kernel-memory" argument.
So your problem then is that you want to start a container without the
--kernel-mem
11 matches
Mail list logo
