Skip to content

docs: offline (air-gapped) installs #4644

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 19, 2022
Merged

docs: offline (air-gapped) installs #4644

merged 2 commits into from
Oct 19, 2022

Conversation

bpmct
Copy link
Member

@bpmct bpmct commented Oct 19, 2022

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.

@bpmct bpmct changed the title chore: add docs for offline (air-gapped) installs docs: offline (air-gapped) installs Oct 19, 2022
@bpmct bpmct merged commit 0727c98 into main Oct 19, 2022
@bpmct bpmct deleted the bpmct/airgap branch October 19, 2022 11:12
@github-actions github-actions bot locked and limited conversation to collaborators Oct 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use without a network connection (air gapped)
3 participants