# Privileged containers causing high CPU

**URL:** <https://forums.suse.com/t/privileged-containers-causing-high-cpu/2530>\
**Category:** General\
**Created:** [April 20, 2016, 12:05am UTC](https://forums.suse.com/t/privileged-containers-causing-high-cpu/2530 "2016-04-20T00:05:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cloudlady911](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/cloudlady911/32/782_2.png) [@cloudlady911](https://forums.suse.com/u/cloudlady911)\
**Post date:** [April 20, 2016, 12:05am UTC](https://forums.suse.com/t/privileged-containers-causing-high-cpu/2530/1 "2016-04-20T00:05:55Z")

</div>

I am trying to setup ConvoyNFS, following the instructions in the December Meetup video. During the discussion he installs a “simple” NFS server from CPUGuy83. Here is the docker compose he shows as an example:

```
nfs:
  log_driver: ''
  labels:
    io.rancher.scheduler.affinity:host_label: service=nfs
  command:
  - /exports
  log_opt: {}
  image: cpuguy83/nfs-server
  privileged: true
  volumes:
  - /exports

```

However it appears as tho running the container in privileged mode is causing the CPU to be pegged.

![](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/1/16d603e1340977cfbdf1c9962b136e4dd825b1e2.png)

I have read here ([getty processes at 100% cpu? · Issue #4040 · moby/moby · GitHub](https://github.com/docker/docker/issues/4040)) that this is a known issue if you run containers in priveliged mode, but so far have not found a fix.

I am posting this here, because I have noticed this behaviour with other containers that launch through Rancher.

---

<div class="post-metadata">

**Author:** ![cloudlady911](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/cloudlady911/32/782_2.png) [@cloudlady911](https://forums.suse.com/u/cloudlady911)\
**Post date:** [April 20, 2016, 8:12pm UTC](https://forums.suse.com/t/privileged-containers-causing-high-cpu/2530/2 "2016-04-20T20:12:55Z")

</div>

I verified that it was the NFS container that was causing this. If I stop the container and kill the getty process, then CPU goes back to normal. Starting the container, causes the process to re-appear and use up all the CPU.

Perhaps there is a better way to launch this container without privileged? Perhaps there is a better way to do NFS testing?

I tested glusterfs and it worked okay, however really just don’t want to have to have 3 servers minimum to use it. I want all the source volumes to “live” on one server for now.

What alternatives are there that will let me create a simple NFS server which I can connect ConvoyNFS too?