Ghost update fails - Command failed: yarn install --no-emoji --no-progress

I recently installed Ghost myself on a DigitalOcean droplet (not using the marketplace image, but just by following this guide: How to install & setup Ghost on Ubuntu 20.04 or 22.04

Everything has been working fine and I’ve been backing up and installing the most recent minor updates no problem until today.

I ran ghost update it errored out. Here’s the detailed log output generated:

Debug Information:
    OS: Ubuntu, v22.04.3 LTS
    Node Version: v18.18.2
    Ghost Version: 5.72.1
    Ghost-CLI Version: 1.25.3
    Environment: production
    Command: 'ghost update'
Message: Command failed: yarn install --no-emoji --no-progress
warning ghost@5.73.0: The engine "cli" appears to be invalid.
warning Resolution field "@elastic/elasticsearch@8.5.0" is incompatible with requested version "@elastic/elasticsearch@8.10.0"
warning Resolution field "moment@2.24.0" is incompatible with requested version "moment@^2.29.1"
warning Resolution field "moment@2.24.0" is incompatible with requested version "moment@2.29.1"
warning Resolution field "moment@2.24.0" is incompatible with requested version "moment@^2.27.0"
warning Resolution field "moment-timezone@0.5.23" is incompatible with requested version "moment-timezone@^0.5.31"
warning Resolution field "moment@2.24.0" is incompatible with requested version "moment@2.29.4"
warning Resolution field "moment@2.24.0" is incompatible with requested version "moment@2.29.4"
warning Resolution field "moment-timezone@0.5.23" is incompatible with requested version "moment-timezone@0.5.34"
warning Resolution field "moment@2.24.0" is incompatible with requested version "moment@2.29.1"
warning Resolution field "moment@2.24.0" is incompatible with requested version "moment@2.29.3"
error "components/tryghost-admin-x-design-system-5.73.0.tgz": Tarball is not in network and can not be located in cache (["/var/www/renoproject.org/versions/5.73.0/components/tryghost-admin-x-design-system-5.73.0.tgz","/home/jambalaya/.cache/yarn/v6/.tmp/2916df55fe96f0c1c5e348c396ff891b/.yarn-tarball.tgz"])

yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Exit code: 1

--------------- stdout ---------------
yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.


--------------- stderr ---------------
warning ghost@5.73.0: The engine "cli" appears to be invalid.
warning Resolution field "@elastic/elasticsearch@8.5.0" is incompatible with requested version "@elastic/elasticsearch@8.10.0"
warning Resolution field "moment@2.24.0" is incompatible with requested version "moment@^2.29.1"
warning Resolution field "moment@2.24.0" is incompatible with requested version "moment@2.29.1"
warning Resolution field "moment@2.24.0" is incompatible with requested version "moment@^2.27.0"
warning Resolution field "moment-timezone@0.5.23" is incompatible with requested version "moment-timezone@^0.5.31"
warning Resolution field "moment@2.24.0" is incompatible with requested version "moment@2.29.4"
warning Resolution field "moment@2.24.0" is incompatible with requested version "moment@2.29.4"
warning Resolution field "moment-timezone@0.5.23" is incompatible with requested version "moment-timezone@0.5.34"
warning Resolution field "moment@2.24.0" is incompatible with requested version "moment@2.29.1"
warning Resolution field "moment@2.24.0" is incompatible with requested version "moment@2.29.3"
error "components/tryghost-admin-x-design-system-5.73.0.tgz": Tarball is not in network and can not be located in cache (["/var/www/renoproject.org/versions/5.73.0/components/tryghost-admin-x-design-system-5.73.0.tgz","/home/jambalaya/.cache/yarn/v6/.tmp/2916df55fe96f0c1c5e348c396ff891b/.yarn-tarball.tgz"])

I tried some of the things I read on this forum when I searched for more info which included figuring out which version of yarn I have installed (apparently I don’t have yarn installed because I got no output from yarn --version and was told it wasn’t found). Just incase, I ran ghost buster to clear the yarn cache incase there was a version of yarn bundled in with Ghost-CLI I didn’t know about or have access to and I rebooted the entire droplet to no avail.

Does anyone have any ideas what my issue might be and how to successfully upgrade?

Thank you.

Also, if it’s as simple as just installing yarn on my system, is there a recommended version to use with Ghost?

I’ve only not tried to install yarn because I’ve read mixed things that seem to imply somehow yarn is a part of Ghost-CLI already and I didn’t want to cause any conflicts.

Thanks.

For what it’s worth, I’m seeing the same error on my self-hosted Ghost this evening.

I installed it a week or two ago (version 5.71.0), successfully did a ghost update to 5.72.0 about a week later… but now ghost update is failing. (Ghost itself has been working great all this time.)

Same

error "components/tryghost-admin-x-design-system-5.73.0.tgz": Tarball is not in network and can not be located in cache

as you’re seeing.

Also, I also just tried to do a fresh ghost install in another directory for another new blog site and that seems to be failing with the same error.

Tried the ghost buster cache clear, also sudo npm install yarn -g (which gets a command-line yarn) but no joy.

Puzzled… hoping it’s an “upstream issue” and someone will do some magic that’ll fix it.

1 Like

I have the same issue on two self-installed Ghost instances. This must be a Ghost not a local fix.

Fwiw, also being discussed on Github with lots of reports.

The release also failed a number of build tests. so not really clear why it was pushed.

1 Like

The release has been pulled from NPM as it contained a broken build that appears related to a recent change in the Admin components. We’ll be re-releasing early next week and investigating why the automated release failed and still went out.

3 Likes

Thanks for the patience everyone :slightly_smiling_face:

This was due to an error with the automated publishing. This should now be fixed in v5.73.1 and we’re doing a portmortem internally to avoid this again in the future.

4 Likes

I am getting this problem with a local install
Mac OS

I solved this problem by setting the environmental variable to an empty string and clearing the yarn cache

1 Like