Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

8
  • You’re probably missing kernel support for “devices” control groups.
    – Daniel B
    Commented Apr 24, 2017 at 13:34
  • Why exactly do you want to do this in a container? It can be done more easily by setting up a second network namespace, which is the same thing the container does, except there is none of the container overhead. Commented Apr 24, 2017 at 13:52
  • @MariusMatutiae : It's for test purposes, I want a fully functionnal linux container without having to run a virtual machine.
    – omega
    Commented Apr 24, 2017 at 18:49
  • @DanielB: How could I check that ? What could I do for ?
    – omega
    Commented Apr 24, 2017 at 18:50
  • So I installed the current Debian from scratch and the option works fine. Please verify that all cgroup filesystems (cpuset, cpu/cpuacct, devices, freezer, net_cls/net_prio, blkio and perf_event) are correctly mounted at /sys/fs/cgroup. If not, there may be an error somewhere in your boot configuration. Are you running systemd? Is your Debian installation old and upgrated?
    – Daniel B
    Commented Apr 24, 2017 at 20:41