The main reason is that docker container is not a Virtual Machine, so it doesn't provide all of the architecture in the same way that a Virtual Machine might. The underlying infrastructure of docker containers is configured on the Host system, not within the container itself
These tests use brctl and sysctl. You can use --privileged flag ('docker run' command) for brctl. What about sysctl? You can use sysctl commands with docker-client. But you can not use it inside a container.
It would be very cool if the tests were fixed so that they work in docker containers.
There are no enough resources to raise the pool of virtual machines sometimes. People use containers in this case.
There are two tests that fail in docker container: paste.openstack .org/show/ 722171/
http://
The main reason is that docker container is not a Virtual Machine, so it doesn't provide all of the architecture in the same way that a Virtual Machine might. The underlying infrastructure of docker containers is configured on the Host system, not within the container itself
These tests use brctl and sysctl. You can use --privileged flag ('docker run' command) for brctl. What about sysctl? You can use sysctl commands with docker-client. But you can not use it inside a container.
It would be very cool if the tests were fixed so that they work in docker containers.