Container fails to launch

[WojoJustin]

Preliminary checklist

• I am using the latest stable version of DDEV
• I am using the latest stable version of this add-on

Expected Behavior

ddev can start.

Actual Behavior

This was working with the base setup instructions. Tried to do modifications to the .yaml files and now it won't start the container with the add on.

Project images built in 1s.
 Network ddev-<project-name>_default  Created
 Container ddev-<project-name>-elasticsearch  Created
 Container ddev-<project-name>-web  Created
 Container ddev-<project-name>-db  Created
 Container ddev-<project-name>-web  Started
 Container ddev-<project-name>-elasticsearch  Started
 Container ddev-<project-name>-db  Started
Waiting for containers to become ready: [web db]
Starting ddev-router if necessary...
 Container ddev-router  Created
 Container ddev-router  Started
Waiting 120s for additional project containers [elasticsearch] to become ready...

Failed to restart <project-name>: 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.
The error was 'ddev-<project-name>-elasticsearch container exited.
Troubleshoot this with these commands:

  - ddev logs -s elasticsearch
  - docker logs ddev-<project-name>-elasticsearch
  - docker inspect --format "{{ json .State.Health }}" ddev-<project-name>-elasticsearch | docker run -i --rm ddev/ddev-utilities jq -r
'

Steps To Reproduce

This is a very basic ddev install with WP as the template. I tried adding the elasticsearch add-on as instructed. It was working at first but I needed to make adjustments to heap size. After running a few commands and getting no progress, attempted to update the elasticsearch image version.

Reproduction steps are hard to do because I tried doing a docker system prune and restarting the docker instances. I ran ddev stop. Only way to get this error is to try adding the elasticsearch back in.

Anything else?

I'm assuming there's a ddev caching issue going on but I'm unsure how to resolve that, since I pruned the docker instances and tried doing everything fresh again.

[rfay]

Hi and welcome @WojoJustin - It gives you a couple of things to check there, which are the important thing to do, please do those and report the result:

  - ddev logs -s elasticsearch
  - docker logs ddev-<project-name>-elasticsearch
  - docker inspect --format "{{ json .State.Health }}" ddev-<project-name>-elasticsearch | docker run -i --rm ddev/ddev-utilities jq -r

It would help if you do ddev debug test and attach the result file from that as well. Then we'd understand your environment more.

[stasadev]

Remove the Elasticsearch volume as described in https://github.com/ddev/ddev-elasticsearch#switching-between-elasticsearch-7-and-8

Run it inside the project directory.

[WojoJustin]

Attempting to remove the volume gives me the following error:

Error response from daemon: get ddev-<project-name>-elasticsearch: no such volume

[rfay]

That's not the correct command, not sure if it's the doc's fault.

Do a docker volume ls and look for your elasticsearch volume.

Remove it with docker volume rm <volumename>

[stasadev]

@WojoJustin, were you able to figure it out?

If not, provide the output of what was asked above (after installing this add-on):

• ddev debug test
• ddev logs -s elasticsearch

I tried adding the elasticsearch add-on as instructed. It was working at first but I needed to make adjustments to heap size. After running a few commands and getting no progress, attempted to update the elasticsearch image version.

And of course we're asking to do a fresh install of the add-on without any customizations.

Reproduction steps are hard to do because I tried doing a docker system prune and restarting the docker instances. I ran ddev stop. Only way to get this error is to try adding the elasticsearch back in.

docker system prune doesn't remove volumes, that's why it didn't work.