Virtualbox/Vagrant box packager includes hardcoded user information

[axd]

unless following config is used inside Vagrantfile,

      myvm.vm.provider "virtualbox" do |vb|
          # workaround
          vb.customize [ 'modifyvm', :id, '--uartmode1', 'disconnected']
      end

Vagrant box packaging will result in the inclusion of a hardcoded (and apparently totally unrelated) user file path (usually related to the user creating the box, eg /home/user/<filename>) in the box.ovf (XML) file, resulting in errors when another user tries to install (vagrant up) that box.

This file is probably used to configure serial ports, but in this case a local logfile path somehow ends up in this setting.

[Socratis]

Vagrant is a program that relies on VirtualBox but modifies its configuration files in unknown ways to us. They have their own ​Vagrant support channels. Do you have this problem with a standalone version of VirtualBox?

[axd]

Thx for your reply.

I was in doubt who exactly was managing the Vagrant/Virtualbox packaging plugin (vagrant? virtualbox?). Today I filed a fresh issue at ​https://github.com/hashicorp/vagrant/issues/9425, pls consider this issue closed if Virtualbox is no actor in this scenario.

thx