Somme software does not work inside docker container
Environment
- Red Hat Enterprise Linux 7.0
- Red Hat Enterprise Atomic (beta)
Issue
- Some Red Hat software does not "out of the box" work inside docker containers.
Root Cause
In some cases software that does not run in a docker container likely has a specific reason. These reason can range from, the software does not span namespaces, or can't access interposes communications with the host, etc. In these cases this software often needs to run in a super privileged container.
Specifically you might need examine the software, and how it interacts with the kernel to see what options (--privileged --net=host --ipc=host --pid=host) need to be supplied to the container, so that it can interact with the kernel on the host system.
Example (of a super privileged container):
docker run -t -i --rm --privileged --net=host --ipc=host --pid=host docker-registry.usersys.redhat.com/atomicga/rheltools:latest bash
By default docker walls off parts of the kernel, so that containers can't get access sensitive items (that only root can uses). Supplying the options above allows you to remove these wall, and provide more functionality to the container, making it look as if it were on the host.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.