Container file corruption after a major crash

Hi,

Today my computer “went dark” like a bluescreen, except… no blue screen)
But when it came back up, my development environment shows an error…

I have never seen this error before,
A restart of VSCODE or reboot did not help:

image

remoteContainers-2022-07-06T13-51-29.159Z.log
[2022-07-06T13:51:29.232Z] Start: Resolving Remote
[2022-07-06T13:51:29.232Z] Remote-Containers 0.238.3 in VS Code 1.68.1 (30d9c6cd9483b2cc586687151bcbcd635f373630).
[2022-07-06T13:51:29.254Z] Setting up container for folder or workspace: c:\GitHub3\EmeraBlockEnergyBox
[2022-07-06T13:51:29.259Z] Start: Check Docker is running
[2022-07-06T13:51:29.259Z] Start: Run: docker version --format {{.Server.APIVersion}}
[2022-07-06T13:51:29.557Z] Stop (298 ms): Run: docker version --format {{.Server.APIVersion}}
[2022-07-06T13:51:29.558Z] Server API version: 1.41
[2022-07-06T13:51:29.558Z] Stop (299 ms): Check Docker is running
[2022-07-06T13:51:29.559Z] Start: Run: docker volume ls -q
[2022-07-06T13:51:29.954Z] Stop (395 ms): Run: docker volume ls -q
[2022-07-06T13:51:30.057Z] Start: Run: docker ps -q -a --filter label=vsch.local.folder=c:\GitHub3\EmeraBlockEnergyBox --filter label=vsch.quality=stable
[2022-07-06T13:51:30.544Z] Stop (487 ms): Run: docker ps -q -a --filter label=vsch.local.folder=c:\GitHub3\EmeraBlockEnergyBox --filter label=vsch.quality=stable
[2022-07-06T13:51:30.545Z] Start: Run: docker ps -q -a --filter label=devcontainer.local_folder=c:\GitHub3\EmeraBlockEnergyBox
[2022-07-06T13:51:31.127Z] Stop (582 ms): Run: docker ps -q -a --filter label=devcontainer.local_folder=c:\GitHub3\EmeraBlockEnergyBox
[2022-07-06T13:51:31.128Z] Start: Run: docker inspect --type container 1b68aef54266
[2022-07-06T13:51:31.785Z] Stop (657 ms): Run: docker inspect --type container 1b68aef54266
[2022-07-06T13:51:31.788Z] Start: Run: C:\Users\LeighBoyd\AppData\Local\Programs\Microsoft VS Code\Code.exe c:\Users\LeighBoyd.vscode\extensions\ms-vscode-remote.remote-containers-0.238.3\dist\spec-node\devContainersSpecCLI.js up --user-data-folder c:\Users\LeighBoyd\AppData\Roaming\Code\User\globalStorage\ms-vscode-remote.remote-containers\data --workspace-folder c:\GitHub3\EmeraBlockEnergyBox --workspace-mount-consistency cached --id-label devcontainer.local_folder=c:\GitHub3\EmeraBlockEnergyBox --log-level debug --log-format json --config c:\GitHub3\EmeraBlockEnergyBox.devcontainer\devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root true
[2022-07-06T13:51:32.192Z] remote-containers 0.238.3.
[2022-07-06T13:51:32.192Z] Start: Run: docker buildx version
[2022-07-06T13:51:32.797Z] Stop (605 ms): Run: docker buildx version
[2022-07-06T13:51:32.798Z] Start: Resolving Remote
[2022-07-06T13:51:32.803Z] Start: Run: git rev-parse --show-cdup
[2022-07-06T13:51:32.870Z] Stop (67 ms): Run: git rev-parse --show-cdup
[2022-07-06T13:51:32.873Z] Start: Run: docker ps -q -a --filter label=devcontainer.local_folder=c:\GitHub3\EmeraBlockEnergyBox
[2022-07-06T13:51:33.355Z] Stop (482 ms): Run: docker ps -q -a --filter label=devcontainer.local_folder=c:\GitHub3\EmeraBlockEnergyBox
[2022-07-06T13:51:33.356Z] Start: Run: docker inspect --type container 1b68aef54266
[2022-07-06T13:51:33.812Z] Stop (456 ms): Run: docker inspect --type container 1b68aef54266
[2022-07-06T13:51:33.813Z] Start: Starting container
[2022-07-06T13:51:33.814Z] Start: Run: docker start 1b68aef54266190cdad46ae9feec578ae7a1e7c3f45a1aae079ec24f6c96d215
[2022-07-06T13:51:34.457Z] Stop (643 ms): Run: docker start 1b68aef54266190cdad46ae9feec578ae7a1e7c3f45a1aae079ec24f6c96d215
[2022-07-06T13:51:34.449Z] Error: Command failed: docker start 1b68aef54266190cdad46ae9feec578ae7a1e7c3f45a1aae079ec24f6c96d215
[2022-07-06T13:51:34.449Z] at NR (c:\Users\LeighBoyd.vscode\extensions\ms-vscode-remote.remote-containers-0.238.3\dist\spec-node\devContainersSpecCLI.js:239:1572)
[2022-07-06T13:51:34.449Z] at Jy (c:\Users\LeighBoyd.vscode\extensions\ms-vscode-remote.remote-containers-0.238.3\dist\spec-node\devContainersSpecCLI.js:239:1510)
[2022-07-06T13:51:34.449Z] at processTicksAndRejections (node:internal/process/task_queues:96:5)
[2022-07-06T13:51:34.450Z] at async zR (c:\Users\LeighBoyd.vscode\extensions\ms-vscode-remote.remote-containers-0.238.3\dist\spec-node\devContainersSpecCLI.js:245:2006)
[2022-07-06T13:51:34.450Z] at async nb (c:\Users\LeighBoyd.vscode\extensions\ms-vscode-remote.remote-containers-0.238.3\dist\spec-node\devContainersSpecCLI.js:245:3110)
[2022-07-06T13:51:34.450Z] at async JR (c:\Users\LeighBoyd.vscode\extensions\ms-vscode-remote.remote-containers-0.238.3\dist\spec-node\devContainersSpecCLI.js:245:13046)
[2022-07-06T13:51:34.450Z] at async KR (c:\Users\LeighBoyd.vscode\extensions\ms-vscode-remote.remote-containers-0.238.3\dist\spec-node\devContainersSpecCLI.js:245:12802)
[2022-07-06T13:51:34.458Z] Stop (2670 ms): Run: C:\Users\LeighBoyd\AppData\Local\Programs\Microsoft VS Code\Code.exe c:\Users\LeighBoyd.vscode\extensions\ms-vscode-remote.remote-containers-0.238.3\dist\spec-node\devContainersSpecCLI.js up --user-data-folder c:\Users\LeighBoyd\AppData\Roaming\Code\User\globalStorage\ms-vscode-remote.remote-containers\data --workspace-folder c:\GitHub3\EmeraBlockEnergyBox --workspace-mount-consistency cached --id-label devcontainer.local_folder=c:\GitHub3\EmeraBlockEnergyBox --log-level debug --log-format json --config c:\GitHub3\EmeraBlockEnergyBox.devcontainer\devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root true
[2022-07-06T13:51:34.458Z] Exit code 1
[2022-07-06T13:51:34.462Z] Command failed: C:\Users\LeighBoyd\AppData\Local\Programs\Microsoft VS Code\Code.exe c:\Users\LeighBoyd.vscode\extensions\ms-vscode-remote.remote-containers-0.238.3\dist\spec-node\devContainersSpecCLI.js up --user-data-folder c:\Users\LeighBoyd\AppData\Roaming\Code\User\globalStorage\ms-vscode-remote.remote-containers\data --workspace-folder c:\GitHub3\EmeraBlockEnergyBox --workspace-mount-consistency cached --id-label devcontainer.local_folder=c:\GitHub3\EmeraBlockEnergyBox --log-level debug --log-format json --config c:\GitHub3\EmeraBlockEnergyBox.devcontainer\devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root true
[2022-07-06T13:51:34.462Z] Exit code 1

image

image

I have an older backup, but I dont remember how to get things going from it…

For example
VSCODE

  • open folder
  • “><” open folder in remote container.
  • then it asks me a LOT of questions… I don’t remember what I selected in the past…

update:

I did VSCODE - new window
click on >< in lower left corner:
then: torizon: open folder in container → select the folder
then did a git checkout,
but now I get : unable to start debugging. Unexpected GDB output from command "-ineerpreter-exec console " …

image

I think ive seen this one before… I dont remember how I fixed it…

Greetings @leighjboyd,

I’m not sure what happened here but it sounds like what ever crash occurred on your PC completely messed up the SDK container, and possibly other parts of the project as well it’s hard to tell.

First try this:

  • With VS Code open the folder containing your project. Do not open the project in a remote container yet.
  • On your system remove all container and container images. That way we remove anything that was possibly corrupted from the crash.
  • Now back to your project using VS Code run the command Torizon: rebuild SDK and load in container. This should hopefully rebuild your SDK container from scratch.

If this doesn’t work, then maybe it might just be less trouble to start a new project from scratch and then copy your code and configurations over to this new project.

Best Regards,
Jeremias

I had a backup from about a month ago that I could restore from…
then did a git checkout.

It took all day to try different things but the simplest was to just go back.

Thanks for your awesome support!

Ok glad to hear you were able to recover.