Hello Jason and Dusty,
Thanks for your answers. I finally found the problem. In the current Fedora
Atomic Host, it seems that the proxy must be set in various files in order for
each tools used by the "atomic" command to work. Correct me if I am wrong but
here is a list of the files to modify to setup the proxy:
- /etc/system/system/docker.service.d/http-proxy.conf - to create in
order to set the proxy for docker ;
- /etc/yum.repos.d/fedora.repo & /etc/yum.repos.d/fedora-upate.repo -
to modify in order for rpm-ostree to install packages ;
- /etc/ostree/remote.d/fedora-atomic.conf - to modify in order for
atomic to upgrade host (using the command `atomic host upgrade`) ;
- /etc/atomic.conf - to modify in order to install containers using the
atomic command.
I modified all of those files and now it works perfectly inside my OpenStack
cluster and behind a proxy.
Best regards.
-----Original Message-----
From: Dusty Mabe [mailto:[email protected]]
Sent: Tuesday, June 26, 2018 9:33 PM
To: DRUILHE, REMI; [email protected]
Subject: Re: [atomic] Unable to install using rpm-ostree
On 06/25/2018 05:15 AM, DRUILHE, REMI wrote:
> Hello,
>
> I am trying to deploy a kubernetes on top of the last Fedora Atomic
> distribution (version 28). Because, for now, it is just for test purposes,
> the Atomic servers are virtualized in an OpenStack cluster. I successfully
> installed Atomic and Cockpit using the online documentation. I was able to
> test that there is no new distribution available through both Cockpit and the
> command line using the "atomic" command".
>
> Now, I am trying to setup a kubernetes cluster using the documentation
> provided on:
> _https://www.projectatomic.io/blog/2017/09/running-kubernetes-on-fedor
> a-atomic-26/_ It is for the version 26 but I was not able to find any
> update for the version 28. I successfully pulled the images for kubernetes
> for both the master and the node (even if for the node, the
> f28/kubernetes-proxy, does not exist). But, when I try to install kubeadm
> using rpm-ostree, I got the following error:
>
> error: cannot update repo 'updates': Cannot prepare internal
> mirrorlist: Curl error (28): Timeout was reached for
> https://mirrors.fedoraproject.org/metalink?repo=updates-released-f28&a
> rch=x86_64 [Connection timed out after 30002 milliseconds]
>
> The link is not broken because I can access to it using my browser. And
> because I successfully pulled the images from docker and checked that a new
> version of Atomic is not available, I think my proxy is not the problem.
> Thus, do you have any clue that could help me solve this issue?
>
Hmm. Not sure exactly. Perhaps an intermittent issue? Does it continue to
happen if you keep trying?
Dusty
