Pulling features/modules in dev containers using a pull-through cache #229
rungitringit
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
My customers need to use dev containers, however their development environment is not permitted direct internet access for security reasons. Pull-through caches (container registries) are available for all common registries in the Development environment.
One of my customers has been able to follow the procedure to set up Dev Containers entirely offline, but we aren't entirely offline and the process of doing so is really not ideal.
Is there a supported method for automatically redirecting to a custom container registry?
In other words we need to make VS Code change the fully qualified container image path to a local pull-through cache rather than the original source registry.
PS: The problem is with pulling "features" after the initial Dev Container is pulled. They are always pulled from the internet registry, which fails in this Dev environment.
Thank you in advance!
Beta Was this translation helpful? Give feedback.
All reactions