Replies: 1 comment 1 reply
-
The easiest way would be to build your dev container prior to losing internet access. There is an expectation that you will have internet access when building a dev container. Lots of Features fetch tools, etc dynamically from the internet on installation. The CLI will also attempt several network calls for various reasons. I recently took a flight and (using the dev containers VS Code extension) made sure I launched the dev container before taking off. Other options include:
Again, note that a lot of Features have runtime dependencies on the internet, so you'd likely need to heavily modify any Features that need to access the network. If you have no references to the Feature and think this is a bug, if you could provide us a minimal repro to test against that would be very helpful |
Beta Was this translation helpful? Give feedback.
-
I'm trying to use devcontainers on a machine without Internet access. All access is through a local artifactory. I can use this to specify a feature I want to use, for example:
But I still get an error trying to grab "ghcr.io/devcontainers/features/common-utils". Is there a way to generically specify a different server for dependent features? I tried cloning the common-utils locally and adding that directory to the features map but it still tries to grab the ghcr.io version.
Beta Was this translation helpful? Give feedback.
All reactions