[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Resolving localhost (IPv6 issue?)

Sorry, I meant resolve.conf inside of one of your containers

On Thu, Aug 11, 2016 at 1:35 PM, Ulf Lilleengen <lulf redhat com> wrote:
[root strappi /]# cat /etc/resolv.conf
# Generated by NetworkManager
search redhat.com
# NOTE: the libc resolver may not support more than 3 nameservers.
# The nameservers listed below may not be recognized.
nameserver 2001:4662:afe3:0:8a1f:a1ff:fe2d:34e6

Note that I set the disable_ipv6=1, but I didn't restart openshift/docker after doing it though.

On 08/11/2016 05:48 PM, Clayton Coleman wrote:
Tried this with Fedora 24 and very similar config (but centos7 image)
and I'm able to ping localhost.

$ cat /etc/hosts
# Kubernetes-managed hosts file.
::1localhost ip6-localhost ip6-loopback

I have net.ipv6.conf.all.disable_ipv6 = 1 set - should be possible.

Can you provide your /etc/resolv.conf from inside that image?

On Thu, Aug 11, 2016 at 11:29 AM, Ulf Lilleengen <lulf redhat com
<mailto:lulf redhat com>> wrote:

    OS: Fedora 24
    Docker: 1.10.3

    Docker image:
    Name: gordons/qdrouterd:v10 (based on Fedora 23)

    Nothing special in the images other than that. The issue appeared
    without any significant change other than running the latest
    openshift/origin image.

    On 08/11/2016 04:58 PM, Clayton Coleman wrote:

        That is very strange.  Anything special about the container
        (what OS,
        libraries, glibc version, musl)?  What version of Docker was

        On Wed, Aug 10, 2016 at 3:45 AM, Ulf Lilleengen <lulf redhat com
        <mailto:lulf redhat com>
        <mailto:lulf redhat com <mailto:lulf redhat com>>> wrote:


            We were debugging an issue yesterday where 'localhost' could
        not be
            resolved inside a container in openshift origin
        v1.3.0-alpha.3. I'm
            not sure if this is openshift or kubernetes-related, but
        thought I'd
            ask here first.

            We have two containers running on a pod, and one container is
            connecting to the other using 'localhost'. This has worked
        fine for
            several months, but stopped working yesterday. We resolved
        the issue
            by using We were also able to use the pod
        hostname as well.

            I'm thinking this might be related to IPv6, given that
            seemed to contain IPv6 records for localhost, and the other
            container may be listening on IPv4 only. I tried disabling
        it with
            sysctl net.ipv6.conf.all.disable_ipv6=1 to verify, but I
        still saw
            the same issue.

            sh-4.3$ cat /etc/hosts
            # Kubernetes-managed hosts file.
            ::1     localhost ip6-localhost ip6-loopback
            fe00::0 ip6-localnet
            fe00::0 ip6-mcastprefix
            fe00::1 ip6-allnodes
            fe00::2 ip6-allrouters

            Ulf Lilleengen

            users mailing list
            users lists openshift redhat com
        <mailto:users lists openshift redhat.com>
            <mailto:users lists openshift redhat.com
        <mailto:users lists openshift redhat.com>>




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]