Starting a previously-built devcontainer in VSCode without internet access

[sevberg]

I really enjoy working with devcontainers, and hope to do more so into the future. However the only "pain" that I have is that I must always have a stable internet connection to start my development environment in VSCode, even when I know for a fact that the image is already built properly and there is nothing new to do which requires the internet. As I often find myself working on trains/planes/ or other locations with slow (or perhaps no) internet connection, this has come up more than once and has been a real pain in my side.

To be fair, this is certainly an effect of me using VSCode as my editor and the related devcontainer extension. I've played around a bit with the devcontainer CLI tool, and I've found that I can build a container using the CLI, and then later, when I don't have internet, I can boot-up that container and remote-connect into it with VSCode. However then I miss a lot of the conveniences specific to the devcontainer extension (like automatically setting up other VSCode extensions)

So, in principal this sort of thing is certainly possible. However I don't see a configuration for it in the extension settings. However maybe I'm missing something?

Assuming I'm not, then I think a nice QOL feature would be that we can have an option for "disable auto rebuild on start" or something to that effect in the devcontainer VSCode extension, which instead of trying to rebuild the image simply restarts and connects to the previously used container

[sevberg]

hmm, weird, I've certainly had this problem often in the past. However I just did a sanity check on a recently reinstalled windows system, and I was able to start a previously-build devcontainer environment while disconnected from the internet. Maybe this has been addressed in a recent version update?

Anyway, I'll close this for now since it no longer seems to be an issue...