Skip to content
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

`jumpod` is not working out of the box #20

Closed
temsa opened this Issue Jul 4, 2017 · 7 comments

Comments

Projects
None yet
3 participants
@temsa
Copy link

temsa commented Jul 4, 2017

I was following this tutorial : http://kubernetesbyexample.com/sd/ , yet I could not do the kubectl exec jumpod -i -t -- dig thesvc.default.svc.cluster.local command with success because the jumpod crashes...

Here is the output of kubectl logs jumpod :

Loaded plugins: fastestmirror, ovl


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=container error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error"

@temsa

This comment has been minimized.

Copy link
Author

temsa commented Jul 4, 2017

Note, from my host machine, I can access the mirrorlist without any error :

http://mirror1.evolution-host.com/centos/7/os/x86_64/
http://ftp.rezopole.net/centos/7/os/x86_64/
http://fr.mirror.babylon.network/centos/7/os/x86_64/
http://mirror.ibcp.fr/pub/Centos/7/os/x86_64/
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/
http://ftp.ciril.fr/pub/linux/centos/7/os/x86_64/
http://mirror.centos.org/centos/7/os/x86_64/
ftp://mirror.bytemark.co.uk/centos/7/os/x86_64/
ftp://ftp.free.fr/mirrors/ftp.centos.org/7/os/x86_64/
http://mirror.steadfast.net/centos/7/os/x86_64/

@mhausenblas mhausenblas self-assigned this Jul 4, 2017

@mhausenblas mhausenblas added the bug label Jul 4, 2017

@mhausenblas

This comment has been minimized.

Copy link
Contributor

mhausenblas commented Jul 4, 2017

Interesting. Thanks for flagging this @temsa. Let me have a look into this.

@jorgemoralespou

This comment has been minimized.

Copy link

jorgemoralespou commented Jul 6, 2017

@mhausenblas, looking at the last comment here https://hub.docker.com/_/centos/ it send as if the coffee mirror in the image could be down. Maybe not many mirrors configured in the image. This should be reproducible running that image everywhere. Maybe latest update of the image fixed it, in which case you need to docker pull that image again to get the latest.

@mhausenblas

This comment has been minimized.

Copy link
Contributor

mhausenblas commented Jul 6, 2017

Hmmm @jorgemoralespou and I just launched it and got:

Loaded plugins: fastestmirror, ovl
ovl: Error while doing RPMdb copy-up:
[Errno 13] Permission denied: '/var/lib/rpm/Installtid'
    
Error making cache directory: /var/cache/yum/x86_64/7/base error was: [Errno 13] Permission denied: '/var/cache/yum/x86_64'
@jorgemoralespou

This comment has been minimized.

Copy link

jorgemoralespou commented Jul 6, 2017

@mhausenblas how did you test this?
It's working for me when manually executing that command:

docker run -it centos:7 yum -y install bind-utils && sleep 10000

And this is the image that has been pulled down and used:

centos                                                                 7                   36540f359ca3        12 hours ago        192.5 MB
@mhausenblas

This comment has been minimized.

Copy link
Contributor

mhausenblas commented Jul 6, 2017

@jorgemoralespou I launched it in Minishift using:

$ kubectl create -f https://raw.githubusercontent.com/mhausenblas/kbe/master/specs/sd/jumpod.yaml

… as per the instructions in http://kubernetesbyexample.com/sd/

mhausenblas added a commit that referenced this issue Jul 6, 2017

@mhausenblas

This comment has been minimized.

Copy link
Contributor

mhausenblas commented Jul 6, 2017

@temsa fixed now, can you confirm please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.