You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2016/11/10 00:37:58 UTC

[jira] [Assigned] (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:all-tabpanel ]

Roman Shaposhnik reassigned BIGTOP-2581:
----------------------------------------

    Assignee: Roman Shaposhnik

> 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)