-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
registry facade won't start in air gap network #8462
Comments
re-checked with feb '2022 release. Still the case |
looks releated to the limitations metioned here: #6983 |
@SirLemyDanger Sorry that it took so long but I'm currently adding instructions on how to install Gitpod in an air-gap network with this pull request. Would love to hear if this works for you. |
that worked as far as I can tell. registry-facade is still crashing but it seems that this is now because of #8559
|
Bug description
After a fresh installation of GitPod (Jan'22) the registry facade pod is crashing permanently.
Environment: K3s on Ubuntu
I set up K3s to pull images from a proxy (artifactory) by having a /etc/rancher/k3s/registries.yaml like this:
This works fine; all containers are being pulled and I can manually pull images with
crictl
.However the registry-facade pod tries to access
https://eu.gcr.io/v2/gitpod-core-dev/build/supervisor/manifests/commit-dbe106c19401e780829827dc50a0154c1b93b96c
which times out, as the machine has no direct access to the internet. See log at the end.In a postpressing step of the gitlab.config.yaml I changed the runtime setting to (not sure though if this is a good idea):
error log:
Steps to reproduce
K3s without traeffik, single node; configured with /etc/rancher/k3s/registries.yaml
install GitPod with installer of the Jan'22 release
Workspace affected
No response
Expected behavior
no request to the internet
Example repository
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: