#got my dev engine in an unrecoverable

1 messages · Page 1 of 1 (latest)

shrewd nacelle
#

Can you save the contents of the volume

#

I'll send a command in a sec

#

just plz don't delete the docker volume 😄

shrewd nacelle
#

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

unkempt wadi
shrewd nacelle
# unkempt wadi 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)

unkempt wadi
#

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

shrewd nacelle
#

just the container

unkempt wadi
#

ah I thought the v did that

shrewd nacelle
#

dagger-engine.dev has a named one

unkempt wadi
#

got it, well that explains why the issue persisted then

shrewd nacelle
unkempt wadi
#

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

unkempt wadi
#

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?

unkempt wadi
unkempt wadi
#

yeah its hefty lol

shrewd nacelle
#

well, I started a dev engine with it, and it works totally fine laughcry 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