Proxies are a major PITA. Without having seen the actual kubic image (which one are you using?), I would guess you need to point the docker daemon to the proxy. Unlike the plain shell https_proxy env var, docker expects HTTPS_PROXY var set at startup. On most systems this is set in /etc/sysconfig/docker or somewhere near that. I am only sure for RHEL/Cent
I did set the proxy in the overlay fs in /var/lib/overlay/1/sysconfig/proxy. The proxy shows up in env correctly, also it does work for surfing with w3m curling and also to fetch the release fro k8s but not for the containers unfortunately.
I don’t know how Google does its security for this repository, and it’s not free so there has to be some kind of authentication.
Since your error is “undefined” but then follows to say that it’s “pinging” the location,
How sure are you that the image exists?
Does your method involve setting authentication credentials somewhere and somehow(Since it’s Google, I’d make a wild guess that there should be Oath2 in there somewhere)?
If you have authenticated access, can you browse this repository to see what is in there? Yes, I think there should be docker images in there, it may even be that this repository is supposed to hold only docker images.
And finally,
Are you following a guide somewhere that recommended storing or sharing images at this location?
You’ll have to be more specific about “the Official Kubic guide” you used since I don’t know that any official documentation exists. When I did some experimenting with Kubic, about 2 paragraphs existed and I had to figure things out by translating SUSE guidance into an openSUSE framework which wasn’t straightforward due to different modules, procedures and authentication/licensing/payment models. Today, it looks like the best “official” guidance is posted in the openSUSE Wiki,
Kubic has had its issues gaining usage, probably not the least was the extreme issues I described just to get myself working which I doubt many others would have been successful… In other words, the project concentrated heavily on turning out innovative, quality product but it was entirely built for “paid” CAAS SUSE, and almost no attention was applied to “open” openSUSE. The world needs Kubic, I don’t know if there is a world-accepted version of Kubernetes other than Red Hat’s OpenShift, but Kubic has great potential to be that alternative due to things like the transactional functions (which really needs an abbreviated command very badly. My fingers get a real workout with transactional server).
In a way,
It’s a good lesson in project objectives and resource allocation, the importance of documentation has been noted before but has often been dismissed. But only highly finished products that are written superlatively to be so intuitive and error-free do not need documentation, and those are very, very rare… and hardly to be expected during early Development.
I did talk about the Kubic Wiki. I first tried the arm Images for raspberry and failed (I did not try to much because it was more or less for being bored) No i am trying to set up a kubernetes cluster at work and fail again :D.
I just wanted to figure things out before i buy caasp for our developers.
If your ultimate goal is to deploy caasp,
Then I strongly recommend that you test and experiment on SUSE from the beginning, as I noted available documentation and guides more closely match what you’ll find on SUSE.
You can download and sign up for a temporary license so you’re not out of picket while you’re testing.
I had to configure the evironment of crio.service in /etc/sysconfig/crio.
After I entered the http_proxy and so on there it works. If I had used my brain earlier this would have been an easy task. systemd.services don’t use system env…
When I can find some time, I’ll probably try to take a look at this if someone doesn’t get to this before me…
Environmental variables are commonly set in systemd Unit files, and if the crio service isn’t commonly used for any other purpose should be set correctly by default.
If you haven’t used this kind of bugzilla before, use only links in the top line, ignore everything below. You can do a search to see if anyone has reported something similar, click “new” to create a new issue.
