Return-Path: X-Original-To: apmail-bigtop-user-archive@www.apache.org Delivered-To: apmail-bigtop-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4187D19016 for ; Sat, 30 Apr 2016 20:32:06 +0000 (UTC) Received: (qmail 43039 invoked by uid 500); 30 Apr 2016 20:32:06 -0000 Delivered-To: apmail-bigtop-user-archive@bigtop.apache.org Received: (qmail 42957 invoked by uid 500); 30 Apr 2016 20:32:06 -0000 Mailing-List: contact user-help@bigtop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@bigtop.apache.org Delivered-To: mailing list user@bigtop.apache.org Received: (qmail 42947 invoked by uid 99); 30 Apr 2016 20:32:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Apr 2016 20:32:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 89DB91A003A for ; Sat, 30 Apr 2016 20:32:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.129 X-Spam-Level: ** X-Spam-Status: No, score=2.129 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 0xPxK_F2meYB for ; Sat, 30 Apr 2016 20:32:03 +0000 (UTC) Received: from mail-yw0-f174.google.com (mail-yw0-f174.google.com [209.85.161.174]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id 4400D5F65C for ; Sat, 30 Apr 2016 20:32:03 +0000 (UTC) Received: by mail-yw0-f174.google.com with SMTP id j74so201381365ywg.1 for ; Sat, 30 Apr 2016 13:32:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to; bh=XzyS0TV/NTuqHMb4PlNmvvItvrltPqIeBB0apHk6LJs=; b=QxUCUT+iEa2pJs5Ib9RqdigWvwYk8zRuk4OG1Edp12AgkSSe4i9F7mgeHUoc1mu4Pb +vhXksQo46AlcVqTbAoyIMs2HSRUH8EAITKDVY3Mwb1B36dwAGKbVFOLWTvvRS58aNkK /hDt+OMtYolXMgZ4I12MqTyb85adyWAzUOZRtH5cOipbXQ1+QaizAHnTsKmpB8VbWOo0 gGzmeLBMIjBMf74JrWTHMqRcECtVOsVnhbX0Ye52bvYOF3g28XVtJqo9pScg0WHPICnu JsxHxir+h5sQg8/SycieYLPAe+Tt4k3cVowhv0fWPgi+Wv+wGEhiP6Z4ujEw3U/4OZ4l XHcg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:date:message-id:subject:from :to; bh=XzyS0TV/NTuqHMb4PlNmvvItvrltPqIeBB0apHk6LJs=; b=ETC/brz3ZH4994y9avTEErYyIQHg5/FOO/GeeY2MzfvF/QPEXqKfOUCPE6Vuhf6xGA mwop8HHLwX9PLHnfbjALO1zX0BGDIOfNz8Sal9H1ywX395yOMcN49qemeUxJsLDP3mNZ BpZqDx00jRI9NWESoPPUGOxTpjftmaoCg5XBWMJ/9FQCuPBvWhqadwdTCQQKJ0W7SzSB hUW96K27c8aMfQWMHGarJZUTpO/kHSuhSpIOztv2Rv3LzKhW8liYD9lkfRSxxZIQA3Qo VWGNBXol++RVK6dzy52cxkVFyNtoZyk0QG6iEGvKOY0gBafLSTn7OaSYjuqbLx46dYDo B+Ow== X-Gm-Message-State: AOPr4FUzIzUxzNbNEQsIQSygw36qhCH5tx0M9oBp2I+za80y6ivFTuhkpdC11T1Q6oCg056EyA8NTuX6hHS4gA== MIME-Version: 1.0 X-Received: by 10.129.2.66 with SMTP id 63mr14809829ywc.250.1462048322533; Sat, 30 Apr 2016 13:32:02 -0700 (PDT) Sender: dbist13@gmail.com Received: by 10.13.207.68 with HTTP; Sat, 30 Apr 2016 13:32:02 -0700 (PDT) Date: Sat, 30 Apr 2016 16:32:02 -0400 X-Google-Sender-Auth: -IoGnjgmkk9e-KQoiXnjdf_N1sM Message-ID: Subject: problem standing up docker cluster From: Artem Ervits To: user@bigtop.apache.org Content-Type: multipart/alternative; boundary=001a1140c260e8c3830531b9a66e --001a1140c260e8c3830531b9a66e Content-Type: text/plain; charset=UTF-8 I'm running the procedure in README for 1.1.0. Having issues with deploying a cluster. Complains that user launching the docker VM is not the same as running deployment. Does anyone have steps that do work? I also tried with 1.0 and was not successful. --001a1140c260e8c3830531b9a66e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I'm running the procedure in README for 1.1.0. Having = issues with deploying a cluster. Complains that user launching the docker V= M is not the same as running deployment. Does anyone have steps that do wor= k? I also tried with 1.0 and was not successful.
--001a1140c260e8c3830531b9a66e--