Skip to content
This repository has been archived by the owner on Dec 5, 2022. It is now read-only.

apt-get warning when running cachier on ubuntu 16.04 #175

Closed
sanguis opened this issue May 19, 2016 · 6 comments
Closed

apt-get warning when running cachier on ubuntu 16.04 #175

sanguis opened this issue May 19, 2016 · 6 comments

Comments

@sanguis
Copy link

sanguis commented May 19, 2016

I have a very basic cachier setup on a virtualbox based image.

just running :box based caching

when I run apt-get update I get the bellow output
Can't drop privileges for downloading as file '/var/lib/apt/lists/partial/us.archive.ubuntu.com_ubuntu_dists_xenial_InRelease' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)

the reason being I believe is because the files in _/var/lib/apt/lists/ are all owned by the user vagrant.

How can I change the user to _apt or root?

@sanguis
Copy link
Author

sanguis commented May 19, 2016

I fixed this by adding the bellow to my config

 c.cache.synced_folder_opts = {
     owner: "_apt",
     group: "_apt"
}

@sanguis sanguis closed this as completed May 19, 2016
@edwarnicke
Copy link

sanguis, the fix is not working for me. It seems that apt-get still tries to chown the files, and that of course fails. Any other thoughts?

@lferro9000
Copy link

The configuration currently (vagrant 1.8.4) is:

config.cache.synced_folder_opts = {
owner: "_apt",
group: "_apt"
}

If that doesn't work, you may need to add permissions:

config.cache.synced_folder_opts = {
owner: "_apt",
group: "_apt",
mount_options: ["dmode=777", "fmode=666"]
}

This has been reported as bugs on both ubuntu and debian forums regarding issues with apt-get warnings:

https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1543280

phs added a commit to waylang/infrastructure that referenced this issue Oct 15, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* Since the dev environment is tightly controlled, `make` is acceptable.
* Rspec and serverspec is likewise abandoned for `bats`, a bash testing tool.
* Ditch Ubuntu 14 for 16.
* Ditch WMware, which has problems [1] in the fuse-based shared FS, for virtualbox

The move to ubuntu 16 was prompted by wanting a newer gpg toolchain (no longer interesting), but it is generally the future.

My previous adherence to 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been resolved, see [2].

[1]: vmware/open-vm-tools#90
[2]: fgrehm/vagrant-cachier#175
phs added a commit to waylang/infrastructure that referenced this issue Oct 15, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* Since the dev environment is tightly controlled, `make` is acceptable.
* Rspec and serverspec is likewise abandoned for `bats`, a bash testing tool.
* Ditch Ubuntu 14 for 16.
* Ditch WMware, which has [problems][1] in the fuse-based shared FS, for virtualbox

The move to ubuntu 16 was prompted by wanting a newer gpg toolchain (no longer interesting), but it is generally the future.

My previous adherence to 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been [resolved][2].

[1]: vmware/open-vm-tools#90
[2]: fgrehm/vagrant-cachier#175
phs added a commit to waylang/infrastructure that referenced this issue Oct 15, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* Since the dev environment is tightly controlled, `make` is acceptable.
* Rspec and serverspec is likewise abandoned for `bats`, a bash testing tool.
* Version commit/tag management has been extracted to `scripts/bump-version`.
* Ditch Ubuntu 14 for 16.
* Ditch WMware, which has [problems][1] in the fuse-based shared FS, for virtualbox

The move to ubuntu 16 was prompted by wanting a newer gpg toolchain (no longer interesting), but it is generally the future.

My previous adherence to 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been [resolved][2].

[1]: vmware/open-vm-tools#90
[2]: fgrehm/vagrant-cachier#175
phs added a commit to waylang/infrastructure that referenced this issue Oct 15, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* Since the dev environment is tightly controlled, `make` is acceptable.
* Rspec and serverspec is likewise abandoned for `bats`, a bash testing tool.
* Version commit/tag management has been extracted to `scripts/bump-version`.
* Ditch Ubuntu 14 for 16.
* Ditch WMware, which has [problems][1] in the fuse-based shared FS, for virtualbox

The move to ubuntu 16 was prompted by wanting a newer gpg toolchain (no longer interesting), but it is generally the future.

My previous adherence to 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been [resolved][2].

[1]: vmware/open-vm-tools#90
[2]: fgrehm/vagrant-cachier#175
phs added a commit to waylang/infrastructure that referenced this issue Oct 15, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* Since the dev environment is tightly controlled, `make` is acceptable.
* Rspec and serverspec is likewise abandoned for `bats`, a bash testing tool.
* Version commit/tag management has been extracted to `scripts/bump-version`.
* Ditch Ubuntu 14 for 16.
* Ditch WMware, which has [problems][1] in the fuse-based shared FS, for virtualbox

The move to ubuntu 16 was prompted by wanting a newer gpg toolchain (no longer interesting), but it is generally the future.

My previous adherence to 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been [resolved][2].

[1]: vmware/open-vm-tools#90
[2]: fgrehm/vagrant-cachier#175
phs added a commit to waylang/infrastructure that referenced this issue Oct 17, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* `make` is now the build tool.
* Rspec and serverspec is likewise abandoned for [`bats`][1], a bash testing tool.
* Version commit/tag management has been extracted to `scripts/bump-version`.
* Ditch Ubuntu 14 for 16.
* Ditch VMware, which has [problems][2] in the fuse-based shared FS, for virtualbox

The move to ubuntu 16 was prompted by wanting a newer GPG toolchain (2.1).  However GPG is no longer interesting, as cleanly exposing signing abilities to git within the guest is just too clumsy.  We keep ubuntu 16 since it's the future anyhow.

My previous adherence to ubuntu 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been [resolved][3].

[1]: https://github.com/sstephenson/bats
[2]: vmware/open-vm-tools#90
[3]: fgrehm/vagrant-cachier#175
phs added a commit to waylang/infrastructure that referenced this issue Oct 17, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* `make` is now the build tool.
* Rspec and serverspec is likewise abandoned for [`bats`][1], a bash testing tool.
* Version commit/tag management has been extracted to `scripts/bump-version`.
* Ditch Ubuntu 14 for 16.
* Ditch VMware, which has [problems][2] in the fuse-based shared FS, for virtualbox

The move to ubuntu 16 was prompted by wanting a newer GPG toolchain (2.1).  However GPG is no longer interesting, as cleanly exposing signing abilities to git within the guest is just too clumsy.  We keep ubuntu 16 since it's the future anyhow.

My previous adherence to ubuntu 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been [resolved][3].

[1]: https://github.com/sstephenson/bats
[2]: vmware/open-vm-tools#90
[3]: fgrehm/vagrant-cachier#175
phs added a commit to waylang/infrastructure that referenced this issue Oct 19, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* `make` is now the build tool.
* Rspec and serverspec is likewise abandoned for [`bats`][1], a bash testing tool.
* Version commit/tag management has been extracted to `scripts/bump-version`.
* Ditch Ubuntu 14 for 16.
* Ditch VMware, which has [problems][2] in the fuse-based shared FS, for virtualbox

The move to ubuntu 16 was prompted by wanting a newer GPG toolchain (2.1).  However GPG is no longer interesting, as cleanly exposing signing abilities to git within the guest is just too clumsy.  We keep ubuntu 16 since it's the future anyhow.

My previous adherence to ubuntu 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been [resolved][3].

[1]: https://github.com/sstephenson/bats
[2]: vmware/open-vm-tools#90
[3]: fgrehm/vagrant-cachier#175
phs added a commit to waylang/infrastructure that referenced this issue Oct 19, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* `make` is now the build tool.
* Rspec and serverspec is likewise abandoned for [`bats`][1], a bash testing tool.
* Version commit/tag management has been extracted to `scripts/bump-version`.
* Ditch Ubuntu 14 for 16.
* Ditch VMware, which has [problems][2] in the fuse-based shared FS, for virtualbox

The move to ubuntu 16 was prompted by wanting a newer GPG toolchain (2.1).  However GPG is no longer interesting, as cleanly exposing signing abilities to git within the guest is just too clumsy.  We keep ubuntu 16 since it's the future anyhow.

My previous adherence to ubuntu 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been [resolved][3].

[1]: https://github.com/sstephenson/bats
[2]: vmware/open-vm-tools#90
[3]: fgrehm/vagrant-cachier#175
phs added a commit to waylang/infrastructure that referenced this issue Oct 19, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* `make` is now the build tool.
* Rspec and serverspec is likewise abandoned for [`bats`][1], a bash testing tool.
* Version commit/tag management has been extracted to `bump-version`.
* Ditch Ubuntu 14 for 16.
* Ditch VMware, which has [problems][2] in the fuse-based shared FS, for virtualbox

The move to ubuntu 16 was prompted by wanting a newer GPG toolchain (2.1).  However GPG is no longer interesting, as cleanly exposing signing abilities to git within the guest is just too clumsy.  We keep ubuntu 16 since it's the future anyhow.

My previous adherence to ubuntu 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been [resolved][3].

[1]: https://github.com/sstephenson/bats
[2]: vmware/open-vm-tools#90
[3]: fgrehm/vagrant-cachier#175
phs added a commit to waylang/infrastructure that referenced this issue Oct 19, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* `make` is now the build tool.
* Rspec and serverspec is likewise abandoned for [`bats`][1], a bash testing tool.
* Version commit/tag management has been extracted to `bump-version`.
* Ditch Ubuntu 14 for 16.
* Ditch VMware, which has [problems][2] in the fuse-based shared FS, for virtualbox

The move to ubuntu 16 was prompted by wanting a newer GPG toolchain (2.1).  However GPG is no longer interesting, as cleanly exposing signing abilities to git within the guest is just too clumsy.  We keep ubuntu 16 since it's the future anyhow.

My previous adherence to ubuntu 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been [resolved][3].

[1]: https://github.com/sstephenson/bats
[2]: vmware/open-vm-tools#90
[3]: fgrehm/vagrant-cachier#175
phs added a commit to waylang/infrastructure that referenced this issue Oct 21, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* `make` is now the build tool.
* Rspec and serverspec is likewise abandoned for [`bats`][1], a bash testing tool.
* Version commit/tag management has been extracted to `bump-version`.
* Ditch Ubuntu 14 for 16.
* Ditch VMware, which has [problems][2] in the fuse-based shared FS, for virtualbox

The move to ubuntu 16 was prompted by wanting a newer GPG toolchain (2.1).  However GPG is no longer interesting, as cleanly exposing signing abilities to git within the guest is just too clumsy.  We keep ubuntu 16 since it's the future anyhow.

My previous adherence to ubuntu 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been [resolved][3].

[1]: https://github.com/sstephenson/bats
[2]: vmware/open-vm-tools#90
[3]: fgrehm/vagrant-cachier#175
phs added a commit to waylang/infrastructure that referenced this issue Oct 23, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* `make` is now the build tool.
* Rspec and serverspec is likewise abandoned for [`bats`][1], a bash testing tool.
* Version commit/tag management has been extracted to `bump-version`.
* Ditch Ubuntu 14 for 16.
* Ditch VMware, which has [problems][2] in the fuse-based shared FS, for virtualbox

The move to ubuntu 16 was prompted by wanting a newer GPG toolchain (2.1).  However GPG is no longer interesting, as cleanly exposing signing abilities to git within the guest is just too clumsy.  We keep ubuntu 16 since it's the future anyhow.

My previous adherence to ubuntu 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been [resolved][3].

[1]: https://github.com/sstephenson/bats
[2]: vmware/open-vm-tools#90
[3]: fgrehm/vagrant-cachier#175
phs added a commit to waylang/infrastructure that referenced this issue Oct 23, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* `make` is now the build tool.
* Rspec and serverspec is likewise abandoned for [`bats`][1], a bash testing tool.
* Version commit/tag management has been extracted to `bump-version`.
* Ditch Ubuntu 14 for 16.
* Ditch VMware, which has [problems][2] in the fuse-based shared FS, for virtualbox

The move to ubuntu 16 was prompted by wanting a newer GPG toolchain (2.1).  However GPG is no longer interesting, as cleanly exposing signing abilities to git within the guest is just too clumsy.  We keep ubuntu 16 since it's the future anyhow.

My previous adherence to ubuntu 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been [resolved][3].

[1]: https://github.com/sstephenson/bats
[2]: vmware/open-vm-tools#90
[3]: fgrehm/vagrant-cachier#175
phs added a commit to waylang/infrastructure that referenced this issue Oct 23, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* `make` is now the build tool.
* Rspec and serverspec is likewise abandoned for [`bats`][1], a bash testing tool.
* Version commit/tag management has been extracted to `bump-version`.
* Ditch Ubuntu 14 for 16.
* Ditch VMware, which has [problems][2] in the fuse-based shared FS, for virtualbox

The move to ubuntu 16 was prompted by wanting a newer GPG toolchain (2.1).  However GPG is no longer interesting, as cleanly exposing signing abilities to git within the guest is just too clumsy.  We keep ubuntu 16 since it's the future anyhow.

My previous adherence to ubuntu 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been [resolved][3].

[1]: https://github.com/sstephenson/bats
[2]: vmware/open-vm-tools#90
[3]: fgrehm/vagrant-cachier#175
phs added a commit to waylang/infrastructure that referenced this issue Oct 23, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* `make` is now the build tool.
* Rspec and serverspec is likewise abandoned for [`bats`][1], a bash testing tool.
* Version commit/tag management has been extracted to `bump-version`.
* Ditch Ubuntu 14 for 16.
* Ditch VMware, which has [problems][2] in the fuse-based shared FS, for virtualbox

The move to ubuntu 16 was prompted by wanting a newer GPG toolchain (2.1).  However GPG is no longer interesting, as cleanly exposing signing abilities to git within the guest is just too clumsy.  We keep ubuntu 16 since it's the future anyhow.

My previous adherence to ubuntu 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been [resolved][3].

[1]: https://github.com/sstephenson/bats
[2]: vmware/open-vm-tools#90
[3]: fgrehm/vagrant-cachier#175
phs added a commit to waylang/infrastructure that referenced this issue Oct 24, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* `make` is now the build tool.
* Rspec and serverspec is likewise abandoned for [`bats`][1], a bash testing tool.
* Version commit/tag management has been extracted to `bump-version`.
* Ditch Ubuntu 14 for 16.
* Ditch VMware, which has [problems][2] in the fuse-based shared FS, for virtualbox

The move to ubuntu 16 was prompted by wanting a newer GPG toolchain (2.1).  However GPG is no longer interesting, as cleanly exposing signing abilities to git within the guest is just too clumsy.  We keep ubuntu 16 since it's the future anyhow.

My previous adherence to ubuntu 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been [resolved][3].

[1]: https://github.com/sstephenson/bats
[2]: vmware/open-vm-tools#90
[3]: fgrehm/vagrant-cachier#175
phs added a commit to waylang/infrastructure that referenced this issue Oct 24, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* `make` is now the build tool.
* Rspec and serverspec is likewise abandoned for [`bats`][1], a bash testing tool.
* Version commit/tag management has been extracted to `bump-version`.
* Ditch Ubuntu 14 for 16.
* Ditch VMware, which has [problems][2] in the fuse-based shared FS, for virtualbox

The move to ubuntu 16 was prompted by wanting a newer GPG toolchain (2.1).  However GPG is no longer interesting, as cleanly exposing signing abilities to git within the guest is just too clumsy.  We keep ubuntu 16 since it's the future anyhow.

My previous adherence to ubuntu 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been [resolved][3].

[1]: https://github.com/sstephenson/bats
[2]: vmware/open-vm-tools#90
[3]: fgrehm/vagrant-cachier#175
phs added a commit to waylang/infrastructure that referenced this issue Oct 24, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* `make` is now the build tool.
* Rspec and serverspec is likewise abandoned for [`bats`][1], a bash testing tool.
* Version commit/tag management has been extracted to `bump-version`.
* Ditch Ubuntu 14 for 16.
* Ditch VMware, which has [problems][2] in the fuse-based shared FS, for virtualbox

The move to ubuntu 16 was prompted by wanting a newer GPG toolchain (2.1).  However GPG is no longer interesting, as cleanly exposing signing abilities to git within the guest is just too clumsy.  We keep ubuntu 16 since it's the future anyhow.

My previous adherence to ubuntu 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been [resolved][3].

[1]: https://github.com/sstephenson/bats
[2]: vmware/open-vm-tools#90
[3]: fgrehm/vagrant-cachier#175
phs added a commit to waylang/infrastructure that referenced this issue Oct 24, 2016
Apparently chef can't sit on its hands for a few months without breaking itself.  Out you go!  Once removed, there isn't much argument for ruby either: the next best provisioning tool for this use case is probably shell scripts.

This prompts a number of not-so-small changes:
* `make` is now the build tool.
* Rspec and serverspec is likewise abandoned for [`bats`][1], a bash testing tool.
* Version commit/tag management has been extracted to `bump-version`.
* Ditch Ubuntu 14 for 16.
* Ditch VMware, which has [problems][2] in the fuse-based shared FS, for virtualbox
* `install` grows a `LOCAL` mode, intended to update an existing repo.

The move to ubuntu 16 was prompted by wanting a newer GPG toolchain (2.1).  However GPG is no longer interesting, as cleanly exposing signing abilities to git within the guest is just too clumsy.  We keep ubuntu 16 since it's the future anyhow.

My previous adherence to ubuntu 14 was driven by a problem between `vagrant-cachier` and permissions/ownership problems appearing in 16.  These have been [resolved][3].

[1]: https://github.com/sstephenson/bats
[2]: vmware/open-vm-tools#90
[3]: fgrehm/vagrant-cachier#175
@amontalban
Copy link

amontalban commented Nov 14, 2016

For me the solution was this on Ubuntu Xenial (16.04.1 LTS) on Vagrant 1.8.5:

  if Vagrant.has_plugin?("vagrant-cachier")
    config.cache.scope = :box
    config.cache.synced_folder_opts = {
       owner: "_apt",
    }
  end
root@ubuntu-xenial:~# id _apt
uid=105(_apt) gid=65534(nogroup) groups=65534(nogroup)
root@ubuntu-xenial:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.1 LTS
Release:        16.04
Codename:       xenial

@openfirmware
Copy link

Thanks @amontalban, I was able to fix a kitchen-vagrant setup with that. For anyone else using kitchen-vagrant ~1.0.2, here's how.

Create a new Vagrantfile in the Chef cookbook, e.g. test/ubuntu-1604-Vagrantfile.rb. It has to end with .rb. Contents:

Vagrant.configure("2") do |c|
  if Vagrant.has_plugin?("vagrant-cachier")
    c.cache.synced_folder_opts = {
      owner: "_apt"
    }
  end
end

Then in your .kitchen.yml file, edit your platforms list to include that Vagrantfile for Ubuntu 16.04:

platforms:
  - name: ubuntu-14.04
  - name: ubuntu-16.04
    driver:
      vagrantfiles:
        - test/ubuntu-16.04-Vagrantfile.rb

After destroying and re-creating the test-kitchen vagrant, it will include the custom Vagrant configuration.

@kadamwolfe
Copy link

I just encountered this issue today. Oddly enough vagrant 1.9.6 was also released today. Upgraded vagrant and reinstalled vagrant plugins and the issue was resolved.

patleb added a commit to patleb/deprecated-ext_vagrant that referenced this issue Aug 6, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants