On 8 May 2018 at 10:40, docularxu wrote:
> Github user docularxu commented on the issue:
>
> https://github.com/apache/bigtop/pull/258
>
> When I run
> [bigtop]/provisioner/docker$ ./docker-hadoop.sh -C
> config_centos-7-aarch64.yaml --create 5 --smoke-tests --destroy
> on an aar
Github user nareshgbhat commented on the issue:
https://github.com/apache/bigtop/pull/258
My apologies for late reply. I was on vacation. The patch is conflicting.
We usually follow the official docker image registry. Yes, if the trunk
debian 9 aarch64 image exists it makes sense
Github user docularxu commented on the issue:
https://github.com/apache/bigtop/pull/258
I see. Just found the same by having a closer look of docker-compose.yml.
And clearly,
if run with -c config_debian-8-aarch64.yaml, it has this problem too.
But should a user be warned
Github user JunHe77 commented on the issue:
https://github.com/apache/bigtop/pull/258
The image (bigtop/puppet:trunk-centos-7-aarch64) is not provided on
dockhub. You need to build it locally.
For all valid images at present, pls check here:
https://hub.docker.com/r/bigtop/puppet
Github user docularxu commented on the issue:
https://github.com/apache/bigtop/pull/258
When I run
[bigtop]/provisioner/docker$ ./docker-hadoop.sh -C
config_centos-7-aarch64.yaml --create 5 --smoke-tests --destroy
on an aarch64 machine, I always get this failure:
Github user evans-ye commented on the issue:
https://github.com/apache/bigtop/pull/258
LGTM, thanks for the patch. Will commit shortly.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this fe
Github user nareshgbhat commented on the issue:
https://github.com/apache/bigtop/pull/258
@evans-ye Thanks for pointing. Done.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
en
Github user evans-ye commented on the issue:
https://github.com/apache/bigtop/pull/258
Patch looks good except you should set enable_local_repo to false.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project doe
Github user nareshgbhat commented on the issue:
https://github.com/apache/bigtop/pull/258
@c0s now the repo is pointing to aarch64. Sorry for delay, Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user c0s commented on the issue:
https://github.com/apache/bigtop/pull/258
Well, the change still reads
" +repo:
"http://bigtop-repos.s3.amazonaws.com/releases/1.2.0/centos/7/x86_64"; "
---
If your project is set up for it, you can reply to this email and have your
reply a
Github user nareshgbhat commented on the issue:
https://github.com/apache/bigtop/pull/258
@c0s it is my mistake, you are right the change should be as below
repo: "http://bigtop-repos.s3.amazonaws.com/releases/1.2.0/centos/7/aarch64";
Should I make this change and verify, re-po
Github user c0s commented on the issue:
https://github.com/apache/bigtop/pull/258
Are you intentionally pointing this to
` repo:
"http://bigtop-repos.s3.amazonaws.com/releases/1.2.0/centos/7/x86_64"; `
I was under the impression this is for AArch64, no?
---
If your project i
12 matches
Mail list logo
