Docker throws two warnings related to cgroup rt period/runtime in UbuntuDovecot throws obsolete warnings,...
Python if-else code style for reduced code for rounding floats
How to make healing in an exploration game interesting
As a new Ubuntu desktop 18.04 LTS user, do I need to use ufw for a firewall or is iptables sufficient?
How do you talk to someone whose loved one is dying?
Is honey really a supersaturated solution? Does heating to un-crystalize redissolve it or melt it?
What is the adequate fee for a reveal operation?
Instead of a Universal Basic Income program, why not implement a "Universal Basic Needs" program?
How to get the n-th line after a grepped one?
Why Choose Less Effective Armour Types?
Is it true that good novels will automatically sell themselves on Amazon (and so on) and there is no need for one to waste time promoting?
Could the Saturn V actually have launched astronauts around Venus?
Print a physical multiplication table
Math equation in non italic font
Bacteria contamination inside a thermos bottle
Official degrees of earth’s rotation per day
How are passwords stolen from companies if they only store hashes?
Do I need to be arrogant to get ahead?
Why does overlay work only on the first tcolorbox?
What's the meaning of a knight fighting a snail in medieval book illustrations?
Brexit - No Deal Rejection
Why one should not leave fingerprints on bulbs and plugs?
Is "upgrade" the right word to use in this context?
If I can solve Sudoku, can I solve the Travelling Salesman Problem (TSP)? If so, how?
Can I use USB data pins as a power source?
Docker throws two warnings related to cgroup rt period/runtime in Ubuntu
Dovecot throws obsolete warnings, even though dovecot.conf updated on Ubuntu 11Why isn't ifconfig available in Ubuntu Docker container?How to change docker lxc/cgroup configuration at runtimeCan you run Docker natively on the new Windows 10 (Ubuntu) bash userspace?Cannot login on Zabbix docker installationDocker Ubuntu image missing many common binarieshow to switch docker runtime between runc and ociCannot install docker on Ubuntu 17.10Transfer docker container between two servers
When I run docker & I get:
INFO[0000] libcontainerd: new containerd process, pid: 3091
INFO[0000] [graphdriver] using prior storage driver: aufs
INFO[0000] Graph migration to content-addressability took 0.00 seconds
WARN[0000] Your kernel does not support cgroup rt period
WARN[0000] Your kernel does not support cgroup rt runtime
INFO[0000] Loading containers: start.
I also get all these warnings:
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (8564990571b56c26f32872031507e77f786b870b27ed3f0b80eebe127ce65164).
WARN[0000] libcontainerd: failed to retrieve container 8564990571b56c26f32872031507e77f786b870b27ed3f0b80eebe127ce65164 state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/8564990571b56c26f32872031507e77f786b870b27ed3f0b80eebe127ce65164/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (c997c7c33a57163106e3de4c470a5f0e5bd3d030c259e62a9d6ea8c292e3551f).
WARN[0000] libcontainerd: failed to retrieve container c997c7c33a57163106e3de4c470a5f0e5bd3d030c259e62a9d6ea8c292e3551f state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/c997c7c33a57163106e3de4c470a5f0e5bd3d030c259e62a9d6ea8c292e3551f/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (28c274e176c9c112f8bc73f6916860665c63f1407ca2670944deee7b6ae2e747).
WARN[0000] libcontainerd: failed to retrieve container 28c274e176c9c112f8bc73f6916860665c63f1407ca2670944deee7b6ae2e747 state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/28c274e176c9c112f8bc73f6916860665c63f1407ca2670944deee7b6ae2e747/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (cca4cbbfb9970b29a26f6cc06622311c0ac789a729810529f35160f742e96c50).
WARN[0000] libcontainerd: failed to retrieve container cca4cbbfb9970b29a26f6cc06622311c0ac789a729810529f35160f742e96c50 state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/cca4cbbfb9970b29a26f6cc06622311c0ac789a729810529f35160f742e96c50/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (fa2937c2ca6cef38dea9de80b68c9a68497739c391393132870e9c6c295ee72b).
WARN[0000] libcontainerd: failed to retrieve container fa2937c2ca6cef38dea9de80b68c9a68497739c391393132870e9c6c295ee72b state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/fa2937c2ca6cef38dea9de80b68c9a68497739c391393132870e9c6c295ee72b/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (b8335587ad37a36a35fc2f1eb57b3b3d91f61af75262eb075b9045664885ee30).
WARN[0000] libcontainerd: failed to retrieve container b8335587ad37a36a35fc2f1eb57b3b3d91f61af75262eb075b9045664885ee30 state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/b8335587ad37a36a35fc2f1eb57b3b3d91f61af75262eb075b9045664885ee30/shm: invalid argument
WARN[0001] libcontainerd: client is out of sync, restore was called on a fully synced container (40d2418b6741c35dd249d5e4c7aefd248fa6f0efa25d7578f81fff06aea93d3b).
WARN[0001] libcontainerd: failed to retrieve container 40d2418b6741c35dd249d5e4c7aefd248fa6f0efa25d7578f81fff06aea93d3b state: rpc error: code = 2 desc = containerd: container not found
WARN[0001] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/40d2418b6741c35dd249d5e4c7aefd248fa6f0efa25d7578f81fff06aea93d3b/shm: invalid argument
lsb_release -a
LSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
Distributor ID: Ubuntu
Description: Ubuntu 17.04
Release: 17.04
Codename: zesty
How can I correct this?
ubuntu docker ubuntu-17.04
asked Aug 10 '17 at 18:50
jnbdzjnbdz
41451833
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
When I run docker & I get:
INFO[0000] libcontainerd: new containerd process, pid: 3091
INFO[0000] [graphdriver] using prior storage driver: aufs
INFO[0000] Graph migration to content-addressability took 0.00 seconds
WARN[0000] Your kernel does not support cgroup rt period
WARN[0000] Your kernel does not support cgroup rt runtime
INFO[0000] Loading containers: start.
I also get all these warnings:
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (8564990571b56c26f32872031507e77f786b870b27ed3f0b80eebe127ce65164).
WARN[0000] libcontainerd: failed to retrieve container 8564990571b56c26f32872031507e77f786b870b27ed3f0b80eebe127ce65164 state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/8564990571b56c26f32872031507e77f786b870b27ed3f0b80eebe127ce65164/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (c997c7c33a57163106e3de4c470a5f0e5bd3d030c259e62a9d6ea8c292e3551f).
WARN[0000] libcontainerd: failed to retrieve container c997c7c33a57163106e3de4c470a5f0e5bd3d030c259e62a9d6ea8c292e3551f state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/c997c7c33a57163106e3de4c470a5f0e5bd3d030c259e62a9d6ea8c292e3551f/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (28c274e176c9c112f8bc73f6916860665c63f1407ca2670944deee7b6ae2e747).
WARN[0000] libcontainerd: failed to retrieve container 28c274e176c9c112f8bc73f6916860665c63f1407ca2670944deee7b6ae2e747 state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/28c274e176c9c112f8bc73f6916860665c63f1407ca2670944deee7b6ae2e747/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (cca4cbbfb9970b29a26f6cc06622311c0ac789a729810529f35160f742e96c50).
WARN[0000] libcontainerd: failed to retrieve container cca4cbbfb9970b29a26f6cc06622311c0ac789a729810529f35160f742e96c50 state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/cca4cbbfb9970b29a26f6cc06622311c0ac789a729810529f35160f742e96c50/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (fa2937c2ca6cef38dea9de80b68c9a68497739c391393132870e9c6c295ee72b).
WARN[0000] libcontainerd: failed to retrieve container fa2937c2ca6cef38dea9de80b68c9a68497739c391393132870e9c6c295ee72b state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/fa2937c2ca6cef38dea9de80b68c9a68497739c391393132870e9c6c295ee72b/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (b8335587ad37a36a35fc2f1eb57b3b3d91f61af75262eb075b9045664885ee30).
WARN[0000] libcontainerd: failed to retrieve container b8335587ad37a36a35fc2f1eb57b3b3d91f61af75262eb075b9045664885ee30 state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/b8335587ad37a36a35fc2f1eb57b3b3d91f61af75262eb075b9045664885ee30/shm: invalid argument
WARN[0001] libcontainerd: client is out of sync, restore was called on a fully synced container (40d2418b6741c35dd249d5e4c7aefd248fa6f0efa25d7578f81fff06aea93d3b).
WARN[0001] libcontainerd: failed to retrieve container 40d2418b6741c35dd249d5e4c7aefd248fa6f0efa25d7578f81fff06aea93d3b state: rpc error: code = 2 desc = containerd: container not found
WARN[0001] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/40d2418b6741c35dd249d5e4c7aefd248fa6f0efa25d7578f81fff06aea93d3b/shm: invalid argument
lsb_release -a
LSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
Distributor ID: Ubuntu
Description: Ubuntu 17.04
Release: 17.04
Codename: zesty
How can I correct this?
ubuntu docker ubuntu-17.04
asked Aug 10 '17 at 18:50
jnbdzjnbdz
41451833
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I see this, too. I haven't decided whether it's a problem, though.
– Limited Atonement
Oct 11 '17 at 19:15
add a comment |
When I run docker & I get:
INFO[0000] libcontainerd: new containerd process, pid: 3091
INFO[0000] [graphdriver] using prior storage driver: aufs
INFO[0000] Graph migration to content-addressability took 0.00 seconds
WARN[0000] Your kernel does not support cgroup rt period
WARN[0000] Your kernel does not support cgroup rt runtime
INFO[0000] Loading containers: start.
I also get all these warnings:
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (8564990571b56c26f32872031507e77f786b870b27ed3f0b80eebe127ce65164).
WARN[0000] libcontainerd: failed to retrieve container 8564990571b56c26f32872031507e77f786b870b27ed3f0b80eebe127ce65164 state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/8564990571b56c26f32872031507e77f786b870b27ed3f0b80eebe127ce65164/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (c997c7c33a57163106e3de4c470a5f0e5bd3d030c259e62a9d6ea8c292e3551f).
WARN[0000] libcontainerd: failed to retrieve container c997c7c33a57163106e3de4c470a5f0e5bd3d030c259e62a9d6ea8c292e3551f state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/c997c7c33a57163106e3de4c470a5f0e5bd3d030c259e62a9d6ea8c292e3551f/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (28c274e176c9c112f8bc73f6916860665c63f1407ca2670944deee7b6ae2e747).
WARN[0000] libcontainerd: failed to retrieve container 28c274e176c9c112f8bc73f6916860665c63f1407ca2670944deee7b6ae2e747 state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/28c274e176c9c112f8bc73f6916860665c63f1407ca2670944deee7b6ae2e747/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (cca4cbbfb9970b29a26f6cc06622311c0ac789a729810529f35160f742e96c50).
WARN[0000] libcontainerd: failed to retrieve container cca4cbbfb9970b29a26f6cc06622311c0ac789a729810529f35160f742e96c50 state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/cca4cbbfb9970b29a26f6cc06622311c0ac789a729810529f35160f742e96c50/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (fa2937c2ca6cef38dea9de80b68c9a68497739c391393132870e9c6c295ee72b).
WARN[0000] libcontainerd: failed to retrieve container fa2937c2ca6cef38dea9de80b68c9a68497739c391393132870e9c6c295ee72b state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/fa2937c2ca6cef38dea9de80b68c9a68497739c391393132870e9c6c295ee72b/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (b8335587ad37a36a35fc2f1eb57b3b3d91f61af75262eb075b9045664885ee30).
WARN[0000] libcontainerd: failed to retrieve container b8335587ad37a36a35fc2f1eb57b3b3d91f61af75262eb075b9045664885ee30 state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/b8335587ad37a36a35fc2f1eb57b3b3d91f61af75262eb075b9045664885ee30/shm: invalid argument
WARN[0001] libcontainerd: client is out of sync, restore was called on a fully synced container (40d2418b6741c35dd249d5e4c7aefd248fa6f0efa25d7578f81fff06aea93d3b).
WARN[0001] libcontainerd: failed to retrieve container 40d2418b6741c35dd249d5e4c7aefd248fa6f0efa25d7578f81fff06aea93d3b state: rpc error: code = 2 desc = containerd: container not found
WARN[0001] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/40d2418b6741c35dd249d5e4c7aefd248fa6f0efa25d7578f81fff06aea93d3b/shm: invalid argument
lsb_release -a
LSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
Distributor ID: Ubuntu
Description: Ubuntu 17.04
Release: 17.04
Codename: zesty
How can I correct this?
ubuntu docker ubuntu-17.04
asked Aug 10 '17 at 18:50
jnbdzjnbdz
41451833
When I run docker & I get:
INFO[0000] libcontainerd: new containerd process, pid: 3091
INFO[0000] [graphdriver] using prior storage driver: aufs
INFO[0000] Graph migration to content-addressability took 0.00 seconds
WARN[0000] Your kernel does not support cgroup rt period
WARN[0000] Your kernel does not support cgroup rt runtime
INFO[0000] Loading containers: start.
I also get all these warnings:
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (8564990571b56c26f32872031507e77f786b870b27ed3f0b80eebe127ce65164).
WARN[0000] libcontainerd: failed to retrieve container 8564990571b56c26f32872031507e77f786b870b27ed3f0b80eebe127ce65164 state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/8564990571b56c26f32872031507e77f786b870b27ed3f0b80eebe127ce65164/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (c997c7c33a57163106e3de4c470a5f0e5bd3d030c259e62a9d6ea8c292e3551f).
WARN[0000] libcontainerd: failed to retrieve container c997c7c33a57163106e3de4c470a5f0e5bd3d030c259e62a9d6ea8c292e3551f state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/c997c7c33a57163106e3de4c470a5f0e5bd3d030c259e62a9d6ea8c292e3551f/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (28c274e176c9c112f8bc73f6916860665c63f1407ca2670944deee7b6ae2e747).
WARN[0000] libcontainerd: failed to retrieve container 28c274e176c9c112f8bc73f6916860665c63f1407ca2670944deee7b6ae2e747 state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/28c274e176c9c112f8bc73f6916860665c63f1407ca2670944deee7b6ae2e747/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (cca4cbbfb9970b29a26f6cc06622311c0ac789a729810529f35160f742e96c50).
WARN[0000] libcontainerd: failed to retrieve container cca4cbbfb9970b29a26f6cc06622311c0ac789a729810529f35160f742e96c50 state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/cca4cbbfb9970b29a26f6cc06622311c0ac789a729810529f35160f742e96c50/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (fa2937c2ca6cef38dea9de80b68c9a68497739c391393132870e9c6c295ee72b).
WARN[0000] libcontainerd: failed to retrieve container fa2937c2ca6cef38dea9de80b68c9a68497739c391393132870e9c6c295ee72b state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/fa2937c2ca6cef38dea9de80b68c9a68497739c391393132870e9c6c295ee72b/shm: invalid argument
WARN[0000] libcontainerd: client is out of sync, restore was called on a fully synced container (b8335587ad37a36a35fc2f1eb57b3b3d91f61af75262eb075b9045664885ee30).
WARN[0000] libcontainerd: failed to retrieve container b8335587ad37a36a35fc2f1eb57b3b3d91f61af75262eb075b9045664885ee30 state: rpc error: code = 2 desc = containerd: container not found
WARN[0000] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/b8335587ad37a36a35fc2f1eb57b3b3d91f61af75262eb075b9045664885ee30/shm: invalid argument
WARN[0001] libcontainerd: client is out of sync, restore was called on a fully synced container (40d2418b6741c35dd249d5e4c7aefd248fa6f0efa25d7578f81fff06aea93d3b).
WARN[0001] libcontainerd: failed to retrieve container 40d2418b6741c35dd249d5e4c7aefd248fa6f0efa25d7578f81fff06aea93d3b state: rpc error: code = 2 desc = containerd: container not found
WARN[0001] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/40d2418b6741c35dd249d5e4c7aefd248fa6f0efa25d7578f81fff06aea93d3b/shm: invalid argument
lsb_release -a
LSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
Distributor ID: Ubuntu
Description: Ubuntu 17.04
Release: 17.04
Codename: zesty
How can I correct this?
ubuntu docker ubuntu-17.04
ubuntu docker ubuntu-17.04
asked Aug 10 '17 at 18:50
jnbdzjnbdz
41451833
asked Aug 10 '17 at 18:50
jnbdzjnbdz
41451833
asked Aug 10 '17 at 18:50
jnbdzjnbdz
41451833
asked Aug 10 '17 at 18:50
jnbdzjnbdz
41451833
asked Aug 10 '17 at 18:50
jnbdzjnbdz
41451833
41451833
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I see this, too. I haven't decided whether it's a problem, though.
– Limited Atonement
Oct 11 '17 at 19:15
add a comment |
I see this, too. I haven't decided whether it's a problem, though.
– Limited Atonement
Oct 11 '17 at 19:15
I see this, too. I haven't decided whether it's a problem, though.
– Limited Atonement
Oct 11 '17 at 19:15
I see this, too. I haven't decided whether it's a problem, though.
– Limited Atonement
Oct 11 '17 at 19:15
add a comment |
1 Answer
1
active
oldest
votes
It looks like Cgroups features, required by Docker, are not supported by your current kernel. Are you using Debian?
Anyway, these warnings show that no memory, CPU and swap limitations could be applied to Docker containers.
You should update your Kernel if you want/need them.
answered May 3 '18 at 16:58
José Castillo LemaJosé Castillo Lema
40119
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f868027%2fdocker-throws-two-warnings-related-to-cgroup-rt-period-runtime-in-ubuntu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It looks like Cgroups features, required by Docker, are not supported by your current kernel. Are you using Debian?
Anyway, these warnings show that no memory, CPU and swap limitations could be applied to Docker containers.
You should update your Kernel if you want/need them.
answered May 3 '18 at 16:58
José Castillo LemaJosé Castillo Lema
40119
add a comment |
It looks like Cgroups features, required by Docker, are not supported by your current kernel. Are you using Debian?
Anyway, these warnings show that no memory, CPU and swap limitations could be applied to Docker containers.
You should update your Kernel if you want/need them.
answered May 3 '18 at 16:58
José Castillo LemaJosé Castillo Lema
40119
add a comment |
It looks like Cgroups features, required by Docker, are not supported by your current kernel. Are you using Debian?
Anyway, these warnings show that no memory, CPU and swap limitations could be applied to Docker containers.
You should update your Kernel if you want/need them.
answered May 3 '18 at 16:58
José Castillo LemaJosé Castillo Lema
40119
It looks like Cgroups features, required by Docker, are not supported by your current kernel. Are you using Debian?
Anyway, these warnings show that no memory, CPU and swap limitations could be applied to Docker containers.
You should update your Kernel if you want/need them.
answered May 3 '18 at 16:58
José Castillo LemaJosé Castillo Lema
40119
edited May 4 '18 at 14:59
answered May 3 '18 at 16:58
José Castillo LemaJosé Castillo Lema
40119
answered May 3 '18 at 16:58
José Castillo LemaJosé Castillo Lema
40119
answered May 3 '18 at 16:58
José Castillo LemaJosé Castillo Lema
40119
40119
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f868027%2fdocker-throws-two-warnings-related-to-cgroup-rt-period-runtime-in-ubuntu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I see this, too. I haven't decided whether it's a problem, though.
– Limited Atonement
Oct 11 '17 at 19:15