Error response from daemon: No such container: ddev-router (Docker 29 can't access or delete existing containers) #8054
Description
TL;DR The errors here seem to be a result of a Docker 29 (embedded in Docker Desktop, Colima, Lima) problem.
The symptom is that DDEV (and docker) can see containers that they can't kill.
docker rm -f $(docker ps -aq) results in one or two containers that can't be killed.
The fix is to manually delete the errant cant-be-deleted container inside the Docker VM, technique shown below.
- Docker Desktop.
docker run --rm -it --privileged --pid=host justincormack/nsenter1andrm -rf /var/lib/docker/containers/<containerid>* - Colima:
colima sshandsudo -sand thenrm -rf /var/lib/docker/containers/*and restart. - Lima
limactl shellandrm -rf ~/.local/share/docker/containers/*
It will likely show up on Docker CE in Linux, there the equivalent would be
- Linux Docker CE:
sudo -sandrm -rf /var/lib/docker/containers/*andsudo systemctl restart docker
Output of ddev utility test or ddev utility diagnose
Expand `ddev utility test` diagnostic information
Please make sure you have already looked at troubleshooting guide:
https://docs.ddev.com/en/stable/users/usage/troubleshooting/
Simple things to check:
* Use latest stable DDEV version
* ddev poweroff
* Restart Docker Provider
* Reboot computer
* Temporarily disable VPN and firewall
* Remove customizations like 'docker-compose.*.yaml' and PHP/Apache/Nginx config while debugging.
Resulting output will be written to:
/var/folders/23/kwslw4lj3vv4zslv2jf8tdg00000gp/T/ddev-debug-test.txt
file:///var/folders/23/kwslw4lj3vv4zslv2jf8tdg00000gp/T/ddev-debug-test.txt
Please provide the file for support in Discord or the issue queue.
Doing ddev poweroff but will restart projects at completion
panic: runtime error: index out of range [0] with length 0
goroutine 1 [running]:
github.com/ddev/ddev/pkg/ddevapp.PowerOff()
/home/runner/work/ddev/ddev/pkg/ddevapp/poweroff.go:37 +0x534
github.com/ddev/ddev/cmd/ddev/cmd.init.func30(0x140005fd900?, {0x102320420?, 0x0?, 0x0?})
/home/runner/work/ddev/ddev/cmd/ddev/cmd/debug-test.go:76 +0x474
github.com/spf13/cobra.(*Command).execute(0x1022e1a00, {0x102320420, 0x0, 0x0})
/home/runner/work/ddev/ddev/vendor/github.com/spf13/cobra/command.go:1019 +0x7bc
github.com/spf13/cobra.(*Command).ExecuteC(0x1022e64c0)
/home/runner/work/ddev/ddev/vendor/github.com/spf13/cobra/command.go:1148 +0x350
github.com/spf13/cobra.(*Command).Execute(...)
/home/runner/work/ddev/ddev/vendor/github.com/spf13/cobra/command.go:1071
github.com/ddev/ddev/cmd/ddev/cmd.Execute()
/home/runner/work/ddev/ddev/cmd/ddev/cmd/root.go:117 +0x24
main.main()
/home/runner/work/ddev/ddev/cmd/ddev/main.go:28 +0x8c
Expected Behavior
ddev should start normally.
Actual Behavior
When trying to start a fresh project, this is the output:
Project images built in 3s.
Network ddev-ddev-test_default Created
Container ddev-ddev-test-web Created
Container ddev-ddev-test-db Created
Container ddev-ddev-test-db Started
Container ddev-ddev-test-web Started
You have Mutagen enabled and your 'php' project type doesn't have `upload_dirs` set.
For faster startup and less disk usage, set upload_dirs to where your user-generated files are stored.
If this is intended you can disable this warning with `ddev config --disable-upload-dirs-warning`.
Starting Mutagen sync process...
Mutagen sync flush completed in 1s.
For details on sync status 'ddev mutagen st ddev-test -l'
Waiting for containers to become ready: [web db]
Starting ddev-router if necessary...
Failed to start ddev-test: Error response from daemon: No such container: ddev-router
Steps To Reproduce
No response
Anything else?
Hello. I suddenly have been unable to get ddev working. I somewhat recent updated to Docker Desktop 4.57.0 on a Mac Silicon, maybe a week ago, but things have worked fine until today.
I've tried all the commands to remove/redownload the Docker images, reinstalled the ddev binary (via homebrew), nothing is helping. Seems to be an issue with getting the router started, however I'm not quite sure if it's a ddev or Docker issue. Please help!