inspircd 3 stuck exits due to incorrect paths about inspircd-docker

[SISheogorath]

@Magnus010 So you upgraded from version 2 to version 3?

Do you use docker.compose or a volume? In this case your configs are persistent and therefore you need to migrate them, following the guide from the docs.

If you didn't do any modifications yourself and don't care about the generated certificates, just throw things away be removing the volume.

[Magnus010]

It's deployed via docker-compose, and it was set to take the latest tag. We do not have it volume mounted. We only noticed it was crashing yesterday, and it looks like it pulled down the image about 2 days ago?
I did a docker rm -f and a docker rmi -f on the container and images to clean them out, then pulled them again. Still encountered the errors. Backed the version down to 2.0.27 and it worked again.

[SISheogorath]

docker-compose automatically create a volume for the defined volume at /conf/ for the 2.0 images and it seems like it continues to use them for the newer images.

You can run docker-compose down -v but careful, this will delete all volumes for your compose project. As alternative you should be able to stop and remove the inspircd container, remove the volume that is used with it and then start it as v3 container again.

[Magnus010]

Ah, that is good to know. I had no idea that docker-compose created it's own volumes.
Just ran that command, wiped out the ircd volumes, re-upped the compose file, and it's running fine!
Thanks for the help!