#got my dev engine in an unrecoverable
1 messages · Page 1 of 1 (latest)
Can you save the contents of the volume
I'll send a command in a sec
just plz don't delete the docker volume 😄
docker run --rm -v dagger-engine.dev:/vol:ro -v "$PWD":/backup alpine sh -c 'cd /vol && tar -czf /backup/dagger-engine.dev.tar.gz .'
If it's taking way too long or something lemme know
Also, after this is done you can docker volume rm dagger-engine.dev and it should start from a fresh state
here's the full logs in the meantime
if that command is too slow, codex claims docker run --rm -v dagger-engine.dev:/vol:ro alpine sh -c 'apk add --no-cache zstd >/dev/null && tar -C /vol -cf - . | zstd -T0 -3' > dagger-engine.dev.tar.zst will be faster (and I believe it)
Still going. I'm confused why this volume is so big when the engine was started with docker rm -fv dagger-engine.dev && ./hack/build
docker rm -fv ... doesn't delete the named volume
just the container
ah I thought the v did that
me too for a while, but it's only anonymous volumes I think
dagger-engine.dev has a named one
got it, well that explains why the issue persisted then
obviously don't block your whole day on this, if it's too big to extract out then we can just try again if/when it happens again
i can use the released engine while this runs, so thats ok. On this engine I'm working on the testcontainer-style integration tests, and I suspect some tests did some things to the outer engine rather than the inner engine to get it into this state
Good news, the compression finished. Just uploading it to drive so i can share it
any reason to keep the volume around still or can I delete it and see how things look?
no delete away, thank you
we finally have it uploaded https://drive.google.com/file/d/1_lFSfCfpI1MeBVAIsHIII0XCeKdJe01b/view?usp=sharing
86GB!
thank you again!
yeah its hefty lol
well, I started a dev engine with it, and it works totally fine
admittedly that is on latest main where there was a fix for something that happens during engine start https://github.com/dagger/dagger/pull/11795, which I guess could maybe cause it?
also possible whatever the issue was just didn't transfer from /var/lib/dagger, though I don't know what it would be