Analysis
Since DDEV outlined the correct old path name, it also must be stored somewhere. I've analyzed directory ~/.ddev/project-name/
, but could not find any pointer to the old path name there. It seems that this information is stored at some other place.
Docker Containers
Executing docker ps -a | grep project-name
shows the following:
1f4eb31fc94e drud/ddev-webserver:v1.3.0 "/start.sh" 2 months ago Exited (0) 2 months ago ddev-project-name-web
052ecb7c3e1b drud/phpmyadmin:v1.3.0 "/run.sh phpmyadmin" 2 months ago Exited (0) 2 months ago ddev-project-name-dba
b9d71147a54f drud/ddev-dbserver:v1.3.0 "/docker-entrypoint.…" 2 months ago Exited (0) 2 months ago ddev-project-name-db
And executing docker inspect ddev-project-name-web | grep '/home/old-path/project-name'
shows additional information:
"/home/old-path/project-name/.ddev:/mnt/ddev_config:ro",
"/home/old-path/project-name:/var/www/html:cached"
"Source": "/home/old-path/project-name/.ddev",
"Source": "/home/old-path/project-name",
"com.ddev.approot": "/home/old-path/project-name",
Bingo! The old path name is stored inside Docker containers. And since my (valuable) sources only are mounted to this Docker container, it seems to be safe to remove this container by executing docker rm ddev-project-name-web
. Starting DDEV again in the new directory using ddev start
now works again...
Summary
Given that the DDEV project is named project-name
...
docker rm ddev-project-name-web
cd /home/new-path/project-name
ddev start