Open veyalla opened 4 years ago
Hi @veyalla, thanks for the bug report.
Looks like an upstream dependency changed and now requires a newer Go to build it. I've done the first part of the work to address this: I forked the upstream repo and setup a mechanism to publish binaries for it. Tomorrow I'll follow up and update this project to make use of that binary instead of building it in the vagrant guest.
Amazing, thanks much!
Should be fixed now - at least, I've done a vagrant destroy -f && vagrant up
and could see everything running in the Prometheus targets page, and in the Consul services page.
@ncabatoff Thanks, this got me past the failure, but now running into:
default:
default: Reading state information...
default: unzip is already the newest version (6.0-20ubuntu1).
default: curl is already the newest version (7.47.0-1ubuntu2.14).
default: git is already the newest version (1:2.7.4-0ubuntu1.7).
default: vim is already the newest version (2:7.4.1689-3ubuntu1.3).
default: wget is already the newest version (1.17.1-1ubuntu1.5).
default: jq is already the newest version (1.5+dfsg-1ubuntu0.1).
default: golang-1.11-go is already the newest version (1.11.5+ppa-0ubuntu1~ppa2~ubuntu16.04.1).
default: 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
default: /tmp /home/vagrant
default: Archive: packer_1.3.4_linux_amd64.zip
default: inflating: packer
default: /home/vagrant
default: Archive: /tmp/go-getter_1.4.1_linux_amd64.zip
default: inflating: /usr/local/bin/go-getter
==> default: Running provisioner: make-pkgs (shell)...
default: Running: /var/folders/fh/5kvnjjhn5qz5kyh05gl9hhc40000gn/T/vagrant-shell20200117-51155-xxfkcu.sh
default: 2020/01/18 05:12:19 error hard linking downloads/consul-1.5.3-amd64/consul to bin/consul-1.5.3-amd64: link downloads/consul-1.5.3-amd64/consul bin/consul-1.5.3-amd64: operation not permitted
Does this work on macOS?
Whoops, sorry about that. I've reproduced this issue by moving aside my packages
directory.
Apparently you can't do hard links from within virtualbox on a virtualbox shared folder. I usually run make packages
from outside the VM because downloading is really slow within the VM for me, not sure why. Which is how I let this regression bug creep in.
I'll have a fix out this week. If you're impatient, you could install Go on your host machine and run make packages
from the project root. Then the downloaded files will be seen by the stuff running in the VM via the shared folder, and won't run the problematic code.
I'm mostly using MacOS these days, so everything should "work" there, modulo this issue.
Sounds good, thanks for the tip!
Thanks for these instructions. I got an error when trying
vagrant up
: