Failed to start packt: container(s) failed to become healthy before their configured timeout

selwynpolit commented 6 months ago

On Mac, cloned the repo, cd into the directory, and ran ddev start

Starting packt...
Network ddev-packt_default created
Building project images...
Project images built in 0s.
 Container ddev-packt-selenium-chrome  Created
 Container ddev-packt-storybook  Created
 Container ddev-packt-db  Created
 Container ddev-packt-next  Created
 Container ddev-packt-web  Created
 Container ddev-packt-selenium-chrome  Started
 Container ddev-packt-next  Started
 Container ddev-packt-db  Started
 Container ddev-packt-storybook  Started
 Container ddev-packt-web  Started
Starting Mutagen sync process...
Mutagen sync flush completed in 2s.
For details on sync status 'ddev mutagen st packt -l'
Waiting for web/db containers to become ready: [web db]
Starting ddev-router if necessary...
 Container ddev-router  Created
 Container ddev-router  Started
Waiting for additional project containers to become ready...
Failed to start packt: container(s) failed to become healthy before their configured timeout or in 120 seconds. This might be a problem with the healthcheck and not a functional problem. (container 'next' exited, please use 'ddev logs -s next' to find out why it failed)

Ran: $ ddev logs -s next

yarn install v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/next/-/next-13.5.0.tgz: Request failed \"404 Not Found\"".
info If you think this is a bug, please open a bug report with the information provided in "/app/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
yarn run v1.22.19
$ next dev -p 4000
/bin/sh: 1: next: not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Any suggestions how to proceed. Googling that error didn't show anything really actionable.

lussoluca commented 6 months ago

It seems that next 13.5.0 is no longer available on the yarn registry 🤔

Can you please try to delete next/yarn.lock file and then run ddev restart ?

selwynpolit commented 6 months ago

That got it. Thanks!

lussoluca commented 6 months ago

Thanks for the update.

I've updated the repo to point to an existing version of Next

selwynpolit commented 6 months ago

Sweet! Thanks for the prompt response!

On Wed, Apr 10, 2024 at 10:36 AM Lusso Luca @.***> wrote:

Thanks for the update.

I've updated the repo to point to an existing version of Next

— Reply to this email directly, view it on GitHub https://github.com/PacktPublishing/Modernizing-Drupal-10-Theme-Development/issues/51#issuecomment-2047877797, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAECC4GRRUPQS4X6I4YH2GLY4VL7XAVCNFSM6AAAAABGAS25XOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBXHA3TONZZG4 . You are receiving this because you authored the thread.Message ID: <PacktPublishing/Modernizing-Drupal-10-Theme-Development/issues/51/2047877797 @github.com>

-- Selwyn Polit Read my free Drupal book: https://selwynpolit.github.io/d9book/

PacktPublishing / Modernizing-Drupal-10-Theme-Development

Failed to start packt: container(s) failed to become healthy before their configured timeout #51