Deploy fail when invoke 'wp core is-installed' command

trellis
, , ,
21

Having the same issue all of a sudden…

22

What’s different in your releases then?

23

Weirdly enough I’m also unable to re-deploy my last successful deployment. Followed these steps:

  1. Create new Git branch from last working deployment
  2. Update group_vars production branch
  3. Re-provision
  4. Re-deploy

fatal: [xxxxxx]: FAILED! => {“changed”: false, “cmd”: [“wp”, “core”, “is-installed”, “–skip-plugins”, “–skip-themes”], “delta”: “0:00:00.097099”, “end”: “2024-02-18 07:12:26.826924”, “failed_when_result”: true, “msg”: “non-zero return code”, “rc”: 1, “start”: “2024-02-18 07:12:26.729825”, “stderr”: “Error: This does not seem to be a WordPress installation.\nThe used path is: /srv/www/xxxxxx/releases/20240218071051/web/wp/\nPass --path=path/to/wordpress or run wp core download.”, “stderr_lines”: [“Error: This does not seem to be a WordPress installation.”, “The used path is: /srv/www/xxxxx/releases/20240218071051/web/wp/”, “Pass --path=path/to/wordpress or run wp core download.”], “stdout”: “”, “stdout_lines”: }

Update: I was able to deploy successfully by switching from “roots/wordpress-full”: “6.4.3” to “roots/wordpress”: “6.4.3” so I assume something is going wrong in the packager.

24

roots/wordpress-full does not include roots/wordpress-core-installer. roots/wordpress does. You need a core installer package to use the Composer WP package.

2 Likes