Currently the architecture field does not used by Docker engine, so the
value amd64 also works on ppc64le platform.
Yes, I saw the image was created locally, but it was not used by docker
containerizer tests.
When I run docker conainerizer tests on ppc64le, it still use the alpine
image from
Sorry Zhiwei, just see your email. Yes, I can do that. Just for curious,
are you using
the manifest architecture field in ppc64le?
We already have tests relying on the image created locally. Please see:
runtime_isolator_tests.cpp
What do you mean by "And could you make it create and load the
Hi Gilbert, do you have any updates on about this issue?
When will you use the local build Docker image for Docker related testing?
On Mon, Mar 14, 2016 at 9:44 PM, zhiwei wrote:
> Hi Gibert,
>
> I tested your patch, it works on ppc64le, but there is an issue that the
>
this because the architecture, alpine is x86_64, the power is ppc64le.
this may help in IBM Power.
On Mar 12, 2016 01:10, "Gilbert Song" wrote:
> Hi Zhiwei,
>
> I am trying to understand why 'alpine' is not compatible with IBM Power
> platform. Is it because of the
Hi Zhiwei,
I am trying to understand why 'alpine' is not compatible with IBM Power
platform. Is it because of the image's rootfs?
We currently have a JIRA(https://issues.apache.org/jira/browse/MESOS-4684)
in progress to create a local docker image, which is used for docker
runtime isolator local
Yes, I prefer to create specific mesos test images and make them
configurable in configuration file.
On Fri, Mar 11, 2016 at 6:20 PM, Alex Rukletsov wrote:
> It also looks strange to me that we use "random" containers in Mesos tests.
> The proper way would be to have
It also looks strange to me that we use "random" containers in Mesos tests.
The proper way would be to have "mesos" or "apache" account on docker hub
managed by PMC. Do you think it's worth to set up one or it's too much time
investment?
On Thu, Mar 10, 2016 at 12:19 PM, Jan Schlicht
Hi Zhiwei,
I was thinking about this as well, but for different reasons: Pulling in
Docker images for tests is not the ideal solution. Sure, testing a `sleep
1000` should work, but testing an executor leaves some questions on how to
handle changes/deprecation of the interfaces. It's not a
Hi all,
The Docker related test cases that hardcoded "alpine" as the Docker image
which caused test cases failed on IBM Power platform, since the Docker
image "alpine" is not compatible with IBM Power platform.
And I saw an inline comment by Timothy: "// TODO(tnachen): Use local image
to test if