Yeah, yeah, sigh, it's me again....
Now I am running into a new issue, but I believe, something external happened.
For learning I removed all the downloaded things completely. Then I deleted also
~/.vagrant.d/ in my home and started from the beginning with a new git clone and a new,
but unchanged build.
But now there is a new issue, related to vagrant. Please take a look at the last output.
---- snip ---------
/tmp.debootstrap-gnupg-i9oekjha
*==> box: Box file was not detected as metadata. Adding it directly...*
*==> box: Adding box 'tails-builder-amd64-buster-20210710-de2318f3ae' (v0) for
provider: *
box: Unpacking necessary files from:
file:///space/tails-linux/tails-amd64/tails/tails-
builder-amd64-buster-202
10710-de2318f3ae.box *==> box: Successfully added box 'tails-builder-amd64-
buster-20210710-de2318f3ae' (v0) for 'libvirt'!*
Bringing machine 'default' up with 'libvirt' provider... *==> default: Creating image
(snapshot of base box volume).*
Volume for domain is already created. Please run 'vagrant destroy' first.
rake aborted!
VagrantCommandError: 'vagrant ["up", "--provision"]' command failed with exit status 1
/space/tails-linux/tails-amd64/tails/Rakefile:113:in `rescue in run_vagrant'
/space/tails-linux/tails-amd64/tails/Rakefile:110:in `run_vagrant'
/space/tails-linux/tails-amd64/tails/Rakefile:703:in `block (2 levels) in <top (required)>'
/usr/share/rubygems-integration/all/gems/rake-13.0.3/exe/rake:27:in `<top (required)>'
Caused by:
CommandError: command ["vagrant", "up", "--provision", {:chdir=>"./vagrant"}] failed
with exit status 1
/space/tails-linux/tails-amd64/tails/Rakefile:78:in `run_command'
/space/tails-linux/tails-amd64/tails/Rakefile:111:in `run_vagrant'
/space/tails-linux/tails-amd64/tails/Rakefile:703:in `block (2 levels) in <top (required)>'
/usr/share/rubygems-integration/all/gems/rake-13.0.3/exe/rake:27:in `<top (required)>'
Tasks: TOP => build => vm:up
(See full trace by running task with --trace) *==> default: Domain is not created. Please
run `vagrant up` first.*
---- snap --------
I wasa not lazy, and searched the web. vagrant destroy does not work, and vagrant
global-status is telling me, there is no session running.
And I repeat: I did everything from scratch, reinstalling vagrant and its dependencies,
reinstalling the git-tree and so on.
As everything worked before, and I made no changes, the only conclusion is, that
something external must have changed. Something, I have no influence on.
If I am wrong, please apologize, any help is appreceated.
Best regards and happy hacking.
Hans
