wileyj

ping @CharlieC3 @obycode @kantai interesting issue that i haven't seen before

this was from a node that was at chain tip, and this happened on a restart. @pseudozach can you copy/paste your current chainstate dir? (`ls -alh` is probably fine

https://github.com/stacks-network/stacks-core/blob/next/testnet/stacks-node/src/run_loop/boot_nakamoto.rs#L205 https://github.com/stacks-network/stacks-core/blob/9b377f9c36357d6bdc7df4134c0bfd358c42c651/stackslib/src/net/chat.rs#L2751

this may have been a config issue with the `working_dir` key, but let's leave it open in case it comes up again. i've asked @pseudozach to collect logs in the...

> @wileyj I'd like to assist with this issue. Based on [this Dockerfile](https://github.com/stacks-network/stacks-core/blob/3604b661507614813ae57b5ca36539f0e273d8ce/.github/actions/dockerfiles/Dockerfile.alpine-binary), would it be just adding the stacks-signer output? If so, what the `CMD` would be for that...

> @wileyj, thanks for your reply! I'm new to the repo, but overhauling the CI workflows to accurately reflect the released artifacts sounds like a better, long-term solution. I'll look...

https://github.com/stacks-network/stacks-core/pull/4968

i don't think this is a blockchain issue, but i can check to verify - can you give me more details about how you performed the restore of the data...

additioanlly, if you have the archive file names that would also be helpful.

As noted on the call, I don't believe this is a blockchain issue. i'll move it to the docker repo if you could confirm the order of operations for me...