Open CNYuYang opened 3 years ago
Confirmed it is a bug: builder1 box depends on ubuntu-bionic box build log, and I'm sure the build script doesn't hardcode such a path, but not yet find how to fix it. The workaround is either to build the ubuntu-bionic box by yourself or create an empty directory as below:
sudo mkdir -p /var/engineer365/repos/engineer365-infrastructure/virtualbox/boxes/ubuntu-bionic/
sudo chown -R ${USER}:${USER} /var/engineer365/repos/engineer365-infrastructure/virtualbox/boxes/ubuntu-bionic/
This issue is also collected by README.md FAQ.
Keep it open till we find a solution.
This is a really critical issue. I will edit and open it by English.
I find the root cause. That log file is specified in base ubuntu bionic box, whose Vagrantfile is:
include_vagrantfile = File.expand_path("../include/_Vagrantfile", __FILE__)
load include_vagrantfile if File.exist?(include_vagrantfile)
Vagrant.configure("2") do |config|
config.vm.base_mac = "021D48B0D5B9"
config.vm.provider "virtualbox" do |vb|
vb.customize [ "modifyvm", :id, "--uart1", "0x3F8", "4" ]
vb.customize [ "modifyvm", :id, "--uartmode1", "file", File.join(Dir.pwd, "ubuntu-bionic-18.04-cloudimg-console.log") ]
end
end
And my build folder is /var/engineer365/repos/engineer365-infrastructure/virtualbox/boxes/ubuntu-bionic/
, so the build log is hardcoded during building.
I think the solution is to build the ubuntu bionic box without hardcoded log file path. For now, I don't have experience to build such a box from scratch. Will try it.
Re-post the workaround here:
sudo mkdir -p /var/engineer365/repos/engineer365-infrastructure/virtualbox/boxes/ubuntu-bionic/
sudo chown -R ${USER}:${USER} /var/engineer365/repos/engineer365-infrastructure/virtualbox/boxes/ubuntu-bionic/
Verified in another new machine, found this issue not fixed yet.
Found 2 related issues somewere:
Error message:
Looks like it depends
/var/engineer365/repos/engineer365-infrastructure/virtualbox/boxes/ubuntu-bionic/ubuntu-bionic-18.04-cloudimg-console.log