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

Pod doesn't have inet6 on interface #76491

Open
olamy opened this Issue Apr 12, 2019 · 4 comments

Comments

Projects
None yet
5 participants
@olamy
Copy link

olamy commented Apr 12, 2019

I'm using kube 1.14.1 with ubuntu 18.10 and docker 18.09.2
running an image with docker give me inet6 support:

docker run -it jenkins/jnlp-slave bash
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever

The same image started as a pod doesn;t have the inet6 support

kubectl exec --namespace=build  -ti jenkins-slave-4xd2c bash
jenkins@jenkins-slave-4xd2c:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever

It used to work before upgrading ubuntu (17.10)
I didn;t upgrade anything regarding docker or kubernetes
Thanks

@olamy

This comment has been minimized.

Copy link
Author

olamy commented Apr 12, 2019

/sig bugs
/sig network

@k8s-ci-robot k8s-ci-robot added sig/network and removed needs-sig labels Apr 12, 2019

@olamy

This comment has been minimized.

Copy link
Author

olamy commented Apr 12, 2019

/sig network-bugs

@athenabot

This comment has been minimized.

Copy link

athenabot commented Apr 12, 2019

/triage unresolved

🤖 I am a bot run by @vllry. 👩‍🔬

@joakime

This comment has been minimized.

Copy link

joakime commented Apr 16, 2019

I'm experiencing this same issue.
The choice of ubuntu 18.10 or 18.04.1 seems to make no difference. 17.10 also worked for me.

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.