docs: offline (air-gapped) installs #4644
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #3202. I've tested in a VM detached from the public internet.
The experience here isn't fantastic, but it's better we have the path officially documented. For a number of reasons outlined in the Dockerfile snippet, it's necessary to build a custom image based on the use case.
Most enterprises in offline scenarios will already have a container registry and a Ci/CD platform for pushing images to the registry, but it is an extra step vs. just importing an image. I created #4643 to discuss improvements that can be made but nothing feels intuitive to me at this point.