Hm, now that is interesting. I'm not clear how they manage their URLs, but
it seems like they may have missed a hardcoded value used by their update
functionality.
On Feb 5, 2018 3:01 PM, "Nick Allen" wrote:
> I was experiencing this issue with both Ansible 1.8.1 and 2.0.2.
>
> I just found that
I was experiencing this issue with both Ansible 1.8.1 and 2.0.2.
I just found that now it seems to only spit out that warning when checking
for updates; not when downloading new images. If I remove the older image
to force it to re-download, it does seem to work. But after re-downloading
the ima
I had this problem on a machine running Vagrant 1.8.1. I thought it was
only Ubuntu at first, so I removed some additional boxes and found it to be
a problem for all of them. I didn't see any relevant articles other than
some old stuff talking about a bundled curl command being a problem, but
that
When launching either of the development environments, you are probably
seeing a warning message like this.
Bringing machine 'node1' up with 'virtualbox' provider...
> ...
> ==> node1: There was a problem while downloading the metadata for your box
> ==> node1: to check for updates. This is not an