Error: Couldn't extract WordPress archive.

[cmackler]

terminal output:

==> default: Config value "default_standard" updated successfully; old value was "WordPress-Core"
==> default: The installed coding standards are MySource, PEAR, PHPCS, PSR1, PSR2, Squiz, Zend, WordPress, WordPress-Core, WordPress-Docs, WordPress-Extra and WordPress-VIP
==> default: Installing WordPress (release version) in double/htdocs...
==> default: Downloading WordPress 4.8.2 (en_US)...
==> default: md5 hash verified: 2e8744a702a3d9527782d9135a4c9544
==> default: Error: Couldn't extract WordPress archive. unable to decompress gzipped phar archive "/tmp/wp_59e5118fe9a9e.tar.gz" to temporary file
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=path/to/wordpress or run wp core download.
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=path/to/wordpress or run wp core download.
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=path/to/wordpress or run wp core download.
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=path/to/wordpress or run wp core download.
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=path/to/wordpress or run wp core download.
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=path/to/wordpress or run wp core download.
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=path/to/wordpress or run wp core download.
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=path/to/wordpress or run wp core download.
==> default: fatal: Not a git repository (or any parent up to mount point /srv/www)
==> default: Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
==> default: /srv/www/double
==> default: Installing WordPress (release version) in other/htdocs...
==> default: Downloading WordPress 4.8.2 (en_US)...
==> default: md5 hash verified: 2e8744a702a3d9527782d9135a4c9544
==> default: Error: Couldn't extract WordPress archive. unable to decompress gzipped phar archive "/tmp/wp_59e51198c1e34.tar.gz" to temporary file
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=path/to/wordpress or run wp core download.
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=path/to/wordpress or run wp core download.
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=path/to/wordpress or run wp core download.
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=path/to/wordpress or run wp core download.
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=path/to/wordpress or run wp core download.
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=path/to/wordpress or run wp core download.
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=path/to/wordpress or run wp core download.
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=path/to/wordpress or run wp core download.
==> default: fatal: Not a git repository (or any parent up to mount point /srv/www)
==> default: Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

[cmackler]

Happens whenever I create a new site. Just started happening. Could this be an issue with pulling new version of WP? Totally lost here.

[tedgeving]

I have the same problem. As a temporary solution I downloaded the current version of WordPress and extracted it to the directory created by the install. After that I ran the default install script. It does not fix the problem, but it got my local environment up and running.

Problems seems to be with the compression format, this conversation describes the issue in detail:
wp-cli/wp-cli#4370

[rtpHarry]

I'm seeing this problem as well. It seems a solution has been found in the issue linked above but I'm not too familiar with the inner works of this to know what to do with the info:

wp-cli/wp-cli#4370 (comment)

[tomjn]

vv doesn't fully support VVV 2, and a lot of its features are built into VVV, e.g.

  my-site:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template
    hosts:
      - my-site.test

Will create a WordPress install at http://my-site.test in the www/my-site folder

You can add extra options for multisite, nightlys, etc https://github.com/Varying-Vagrant-Vagrants/custom-site-template/