You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Evans Ye (JIRA)" <ji...@apache.org> on 2017/01/15 08:57:26 UTC

[jira] [Comment Edited] (BIGTOP-2581) Docker Vagrant provisioner fails with boot2docker b/c VM is stuck with old client

    [ https://issues.apache.org/jira/browse/BIGTOP-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823080#comment-15823080 ] 

Evans Ye edited comment on BIGTOP-2581 at 1/15/17 8:57 AM:
-----------------------------------------------------------

Hi [~rshaposhnik]. I think this is no longer valid since I've switch the backend of Docker Provisioner from *Vagrant* to *Docker Compose* (BIGTOP-2253). Vagrant has variety of issues. Even though there's a boot2docker VM, I can recall I've encountered many network issues with B2D. My personal opinion is to count on Docker itself to provide Windows support, i.e. Docker for Windows, just like Docker for Mac. That's why I drop Vagrant and go for Docker's native solution. How do you think?


was (Author: evans_ye):
Hi [~rshaposhnik]. I think this is no longer valid since I've switch the backend of Docker Provisioner from *Vagrant* to *Docker Compose* (BIGTOP-2253). Vagrant has variety of issues. Even though there's a boot2docker VM, I can recall many network issue with B2D. My personal opinion is to count on Docker itself to provide Windows support, i.e. Docker for Windows, just like Docker for Mac. That's why I drop Vagrant and go for Docker's native solution. How do you think?

> Docker Vagrant provisioner fails with boot2docker b/c VM is stuck with old client
> ---------------------------------------------------------------------------------
>
>                 Key: BIGTOP-2581
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-2581
>             Project: Bigtop
>          Issue Type: Bug
>          Components: provisioner
>    Affects Versions: 1.1.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>         Attachments: BIGTOP-2581.patch.txt
>
>
> If you run Docker Vagrant provisioner in the environment where boot2docker VM is required you will see docker agent running within that VM fail to fetch the bigtop/deploy image. This is due to known backward incompatibility in docker clients and Docker hub public service. We need to update boot2docker VM somehow to include the latest client. Any thoughts?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)