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.

Sign up for GitHub

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

Jump to bottom

Static IPv6 address and --ip6 #7511

Closed
hakonhall opened this issue Aug 31, 2020 · 29 comments · Fixed by #12611
Closed

Static IPv6 address and --ip6 #7511

hakonhall opened this issue Aug 31, 2020 · 29 comments · Fixed by #12611
Assignees
@Luap99
Labels
In Progress This issue is actively being worked by the assignee, please do not work on this at this time. kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. network Networking related issue or feature

Comments

@hakonhall
Copy link

/kind feature

Description

We need to start containers with a static IPv6 address: the --ip6 option to podman run. These containers may or may not also have a static IPv4 address (--ip).

This has been mentioned in tickets and comments before, but extracted to this ticket for visibility:
#7265 (comment)
#6114 (comment)

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?

Yes, checked HEAD on master.
@openshift-ci-robot openshift-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 31, 2020
@hakonhall
Copy link
Author

From #6114 (comment) this may already be in progress @mheon ?

@mheon mheon added the Good First Issue This issue would be a good issue for a first time contributor to undertake. label Sep 9, 2020
@apoos-maximus
Copy link

I want to work on this issue !

@mheon
Copy link
Member

mheon commented Sep 9, 2020

Sure, let me assign it to you.

This should mostly involve adding the flag to the command line and passing it through into Libpod, similar to how the existing --ip flag works. Unfortunately, it looks like CNI presently limits us to a static IP or IPv6 address, both cannot be used at the same time.

@rhatdan
Copy link
Member

rhatdan commented Sep 9, 2020

Welcome @apoos-maximus. Looking forward to what you come up with.

@apoos-maximus
Copy link

@rhatdan sure !

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@andrin55
Copy link
Contributor

Hi

Is there any progress on this issue?
With Podman version 2.1.1 it's still not implemented:

[root@container01 ~]# podman run -it --rm --network container_dmz --ip6 2a01:x:x:x::199 alpine ping6 2620:fe::fe -c 4
Error: unknown flag: --ip6

When I start the container on my dualstack macvlan network with IPv4 set statically, it allocates a both address types (just the IPv6 address is dynamic):

[root@container01 ~]# podman run -it --rm --network container_dmz --ip 192.168.115.199 alpine sh
/ # ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 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
2: eth0@if3: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP
    link/ether f6:cc:d5:a7:0c:a5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.115.199/24 brd 192.168.115.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 2a01:x:x:x::9/64 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::f4cc:d5ff:fea7:ca5/64 scope link
       valid_lft forever preferred_lft forever
/ # ping6 google.com
PING google.com (2a00:1450:4001:800::200e): 56 data bytes
64 bytes from 2a00:1450:4001:800::200e: seq=0 ttl=118 time=15.479 ms
64 bytes from 2a00:1450:4001:800::200e: seq=1 ttl=118 time=15.575 ms
^C
--- google.com ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 15.479/15.527/15.575 ms

@mheon
Copy link
Member

mheon commented Oct 14, 2020

Not yet. We want to look into Podman and IPv6 compatibility, but we haven't found the time to do so properly yet.

@rhatdan
Copy link
Member

rhatdan commented Nov 12, 2020

@mheon Some IPv6 code just got merged, did that fix this issue or move us closer?

@mheon
Copy link
Member

mheon commented Nov 12, 2020

No - there are still some pretty fundamental issues with IPv6 and CNI.

@rhatdan rhatdan removed Good First Issue This issue would be a good issue for a first time contributor to undertake. stale-issue labels Nov 23, 2020
@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@rhatdan
Copy link
Member

rhatdan commented Dec 24, 2020

I believe there is a duplicate issue to this one in existence, one of them should be closed.

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@unixfox
Copy link

unixfox commented Jan 24, 2021

Bump

@rhatdan
Copy link
Member

rhatdan commented Jan 25, 2021

@apoos-maximus Did you ever work on this?

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@rhatdan
Copy link
Member

rhatdan commented Feb 26, 2021

@mheon PTAL

@apoos-maximus
Copy link

apoos-maximus commented Apr 5, 2021 •
edited
Loading

Hello! i am sorry I am not getting enough time to work on the issue, deepest apologies !.
Please reassign it to someone else

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@Luap99 Luap99 added the network Networking related issue or feature label Jun 21, 2021
@rugk rugk mentioned this issue Jul 9, 2021
Closed
@Luap99 Luap99 mentioned this issue Sep 14, 2021
Closed
@mzhirnov1
Copy link

Hello! I realy need that in our project. Docker have static IPv6 but I like cri-o in production

@mzhirnov1
Copy link

image

@mheon
Copy link
Member

mheon commented Sep 14, 2021

Podman and CRI-O are different projects - if you need support in CRI-O, please open an issue over there.

This is something we are targeting for the network rework in Podman 4.0.

@mzhirnov1
Copy link

we use podman to run containers. When are you going to release Podman 4.0 ?

@mheon
Copy link
Member

mheon commented Sep 14, 2021

Current target is early next year.

@fansari fansari mentioned this issue Oct 16, 2021
Closed
@anthr76
Copy link

anthr76 commented Nov 17, 2021

Any ways the community can chip in and help? I'm not super familiar with podman CNIs yet but I'm going to read up a bit tonight

@mheon
Copy link
Member

mheon commented Nov 17, 2021

Testing netavark, our new network stack, once it becomes available (we're starting to get close to done, functionality-wise) will be extremely helpful - we'll put out a post once it's ready for testing.

The new network code lives at https://github.com/containers/netavark - we're accepting contributions there, but it's still changing rapidly as things come together.

@Luap99
Copy link
Member

Luap99 commented Dec 15, 2021

Should I add the flag or do we only want to support the --network netname:ip6=fd10::2 syntax, @mheon WDYT?

@mheon
Copy link
Member

mheon commented Dec 15, 2021

We should add the flag for Docker compat's sake

@Luap99
Copy link
Member

Luap99 commented Dec 15, 2021

ack, should be simple to add now

@Luap99 Luap99 assigned Luap99 and unassigned mheon Dec 15, 2021
@Luap99 Luap99 added the In Progress This issue is actively being worked by the assignee, please do not work on this at this time. label Dec 15, 2021
@Luap99 Luap99 mentioned this issue Dec 15, 2021
Merged
Luap99 added a commit to Luap99/libpod that referenced this issue Jan 3, 2022
@Luap99
add --ip6 flag to podman create/run
c496001 
Add the --ipv6 flag to podman create/run and pod create. We support the
--network name:ip6=<ip> syntax now but for docker compat we should also
support the --ip6 flag.
Note that there is no validation if the ip is actually a v6 or v4 address
because the backend does not care either.

Fixes containers#7511

Signed-off-by: Paul Holzinger <[email protected]>
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Luap99 Luap99

Labels
In Progress This issue is actively being worked by the assignee, please do not work on this at this time. kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. network Networking related issue or feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add --ip6 flag to podman create/run Luap99/libpod
10 participants
@rhatdan @andrin55 @unixfox @mheon @hakonhall @anthr76 @openshift-ci-robot @apoos-maximus @Luap99 @mzhirnov1