default_container_timeout not working #5133
Milestone
Comments
|
I think if you just wait for it it will work anyway, even though it says that it timed out. Use |
|
I'm not saying that the default-container-timeout function might not be broken, just that it likely won't affect your work. |
|
@rfay the ddev list reports "db: unhealthy". Perhaps the snapshot is simply too large; it is only 20GB in size. ;-) Thanks! |
|
It will be unhealthy until it completes; does the log still show things happening? WHen you do the snapshot restore it shows you how to watch it. Lots of people have done huge snapshots like this, but you need enough disk allocated to docker to do it. You didn't provide the requested |
|
❯ docker inspect --format "{{json .State.Health }}" ddev-cufpt-db Expand `ddev debug test` diagnostic information |
|
You're on a mac with Docker Desktop. Do you have at least 100GB allocated in "Resources"? It can't know what you're about to do when you bring in a 20GB gzipped snapshot, and it eats an enormous amount. If it's possible to share the snapshot or the source db dump I'll be happy to take a look. |
|
It also looks like you're probably using MySQL 8, true? It seems to be to be tremendously slow. |
|
Yes, I am unable to use a different version for this project. I won't be taking any snapshots for this project. I appreciate the support! |
|
The fundamental thing you were talking about isn't resolved. (default_container_timeout) |
|
You are right, sorry for closing. |
|
I would appreciate if you could test the artifacts in #5154 (comment) @introfini |
|
@rfay doing that now. Just leaving this note: The instructions tell to change the parameter like this "ddev config --default_container_timeout=600" but only this works "ddev config --default-container-timeout 600" |
|
Actually, it's |
3 tasks
|
I confirm that this has somehow reappeared in (at least) DDEV v1.23.0 I use my "hugedb" project and set default_container_timeout to 720, and on |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Expected Behavior
I have a rather large database that I snapshot, but when I try to restore it I get the following error:
I've override the default-container-timeout variable as instructed:
ddev config --default-container-timeout 250Actual Behavior
I still get the error with the same 120 seconds:
Failed to restore snapshot cufpt_20230713113115 for project cufpt: failed to start project for RestoreSnapshot: container(s) failed to become healthy before their configured timeout or in 120 seconds. This may be just a problem with the healthcheck and not a functional problem. (health check timed out: labels map[com.ddev.site-name:cufpt] timed out without becoming healthy, status=, detail= ddev-cufpt-db:starting - more info withdocker inspect --format "{{json .State.Health }}" ddev-cufpt-db)The text was updated successfully, but these errors were encountered: