On Wed, Jul 12, 2017 at 06:55:45PM -0300, Philippe Mathieu-Daudé wrote:
> Hi Daniel,
>
> On 07/12/2017 01:25 PM, Daniel P. Berrange wrote:
> > When trying to debug problems with tests it is natural to set
> > DEBUG=1 when starting the docker environment. Unfortunately
> > this has a side-effect
Fam Zheng writes:
> On Wed, 07/12 17:25, Daniel P. Berrange wrote:
>> When trying to debug problems with tests it is natural to set
>> DEBUG=1 when starting the docker environment. Unfortunately
>> this has a side-effect of enabling an eth0 network interface
>> in the
On Wed, 07/12 17:25, Daniel P. Berrange wrote:
> When trying to debug problems with tests it is natural to set
> DEBUG=1 when starting the docker environment. Unfortunately
> this has a side-effect of enabling an eth0 network interface
> in the container, which changes the operating environment of
On 07/12/2017 06:46 PM, Philippe Mathieu-Daudé wrote:
now trying old debian release:
$ docker run --rm -it debian:wheezy sh -c "cat /etc/debian_version";
echo $?
7.11
0
$ docker run --rm -it debian:wheezy bash -c "cat /etc/debian_version";
echo $?
139
Indeed using debian:wheezy based
Hi Daniel,
On 07/12/2017 01:25 PM, Daniel P. Berrange wrote:
When trying to debug problems with tests it is natural to set
DEBUG=1 when starting the docker environment. Unfortunately
this has a side-effect of enabling an eth0 network interface
in the container, which changes the operating
Hi Alex, Fam,
I wanted to try this patch but got:
$ make docker-test-quick@centos6 NETWORK=1
BUILD centos6
The command '/bin/sh -c yum install -y epel-release' returned a non-zero
code: 139
Traceback (most recent call last):
File "./tests/docker/docker.py", line 382, in