-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
allow creating macvlan network without subnet when using netavark backend #13521
Labels
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
openshift-ci
bot
added
the
kind/feature
Categorizes issue or PR as related to a new feature.
label
Mar 15, 2022
@baude This is DHCP support, I believe? |
@mheon ya this is closer to what @Luap99 mentioned, supporting DHCP would be nice, but it sounds like it might be difficult. In reality, I just need a way to create interfaces with macvlan and have the container manage IP assignment. Currently I have to specify --subnet or else the net create will fail. |
Luap99
added a commit
to Luap99/common
that referenced
this issue
Mar 17, 2022
Network create now uses the ipam driver. This allows the user to configure the ipam driver manually instead of choosing a fixed default. If the ipam driver is `none` no ips will be assigned to this container. This means that only the interfaces are created. This will require a patch in netavark since it rejects the config when no static ips are provided. Ref containers/podman#13521 Signed-off-by: Paul Holzinger <[email protected]>
Luap99
added a commit
to Luap99/common
that referenced
this issue
Mar 18, 2022
Network create now uses the ipam driver. This allows the user to configure the ipam driver manually instead of choosing a fixed default. If the ipam driver is `none` no ips will be assigned to this container. This means that only the interfaces are created. This will require a patch in netavark since it rejects the config when no static ips are provided. Ref containers/podman#13521 Signed-off-by: Paul Holzinger <[email protected]>
Luap99
added a commit
to Luap99/common
that referenced
this issue
Mar 29, 2022
Network create now uses the ipam driver. This allows the user to configure the ipam driver manually instead of choosing a fixed default. If the ipam driver is `none` no ips will be assigned to this container. This means that only the interfaces are created. This will require a patch in netavark since it rejects the config when no static ips are provided. Ref containers/podman#13521 Signed-off-by: Paul Holzinger <[email protected]>
Luap99
added a commit
to Luap99/libpod
that referenced
this issue
Apr 11, 2022
Add a new flag to set the ipam-driver. Also adds a new ipam driver none mode which only creates interfaces but does not assign addresses. Fixes containers#13521 Signed-off-by: Paul Holzinger <[email protected]>
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 20, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
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
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind feature
Description
podman (with netavark) should allow creating a mavlan network without specifying a subnet, for cases where the container is capable of managing its own IP assignment on the network (e.g. running its own dhcp client). Currently
--subnet
is required, orpodman network create -d macvlan
will error out.Steps to reproduce the issue:
podman network create -d macvlan foo
error that
--subnet
is requiredDescribe the results you received:
Error: macvlan driver needs at least one subnet specified, DHCP is not supported with netavark
Describe the results you expected:
New macvlan network created with no IP management by podman
Additional information you deem important (e.g. issue happens only occasionally):
This was discussed briefly in chat with @Luap99. Also related: containers/netavark#152
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
(Yes)/No
Additional environment details (AWS, VirtualBox, physical, etc.):
Alpine Linux Edge
The text was updated successfully, but these errors were encountered: