Skip to content
This repository was archived by the owner on Dec 26, 2017. It is now read-only.
This repository was archived by the owner on Dec 26, 2017. It is now read-only.

berkshelf shares the wrong folder when bringing up new vagrant box #295

@ccope

Description

@ccope

Steps to repro:
vagrant destroy && vagrant box remove (your box name)
vagrant up --provision

Chef run will fail due to missing cookbooks (like apt)

This only occurs when the box is added. I see on the first run it vendors the cookbooks into a shelf (in (~/.berkshelf/vagrant-berkshelf/shelves/...), but then it tries sharing the main project 'cookbooks' folder (next to my Vagrantfile) rather than the shelf. vagrant reload && vagrant provision will correctly mount the shelf instead.

Versions:
Vagrant 1.7.4, 1.8.1
ChefDK 0.8.0, 0.10.0
vagrant-berkshelf 4.0.4, 4.1.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions