I’ve been playing with this a bit today. I unpinned CodeRoad, so if you update your rdb-alpha repo, it should install CodeRoad when you load the container.
I believe it was pinned because of the other issues we are having. VSCode extensions can save things to your computer (outside the container), even when running in a container. For instance, maybe the tutorial and step you are on - and it persists even if you delete docker containers/volumes/etc - so docker isn’t the issue as far as I can tell. So it was opening to the middle of a course after rebuilding the container and would be stuck there.
I believe the bottom two commands that @f.labarca.mercado found will clean up that local storage and allow you to start fresh - note that they are OS specific and can delete storage for other extension (the bottom one can I think anyway). I found an alternative workaround - not sure if it’s any better…
- Go to the
rdb-alphafolder in the terminal - Run
code --user-data-dir ./vscode-profile --extensions-dir ./vscode-extensions .
This sets the path for VSCode’s data folders. vscode-profile and vscode-extensions folders will be created in the rdb-alpha folder when you launch it like this - and those will be used instead of the ones elsewhere on your system. Since the folders are empty, you will need to:
- Install the
dev-containersextension again (You should get a little prompt to install it) - and: - Run
Reopen in Container(You should get a little prompt for that too).
Now you can launch CodeRoad as usual and start a fresh course. If you close the window while in the middle of a course, you should be able to continue with the Reopen in container command (not Rebuild and Reopen). To start fresh again (start a different course), delete those two folders (vscode-profile and vscode-extensions) and repeat steps 1 and 2.
I will see if I can find a way to make running these easier.