Uploaded image for project: 'Container Tools'
  1. Container Tools
  2. RUN-4240

[RFE] [Container-libs PR] Require Support multiple address/prefixes per interface

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • podman
    • 3
    • rhel-container-tools
    • RUN 285
    • Moderate

      The goal of this card is to merge the PR that adapts container-libs to support a new Netavark feature.

      PR: https://github.com/containers/container-libs/pull/557

      What were you trying to do that didn't work?

      There is a use-case for configuring multiple IP addresses per (mavclan/ipvlan) interface in a rootful container that does not have NET_ADMIN capability for hardening purposes. Those IP addresses belong to the same large subnet.

      This is a supported configuration in Linux kernel. https://www.kernel.org/doc/html/latest/networking/alias.html

      The ask is to provide option in the `podman run` command so that the IP addresses are setup as soon as the container is up and `podman inspect` can show the configured IP addresses for automation purpose.

      Describe the impact to you or the business
      Usecase is to assign multiple IP addresses for their large segment interface to backup the infrastructure from different client segments. One can achieve this in BYO and other systems where multiple IP addresses can be configured.

              jrodak Jan Rodák
              rhn-support-sachisha Sachin Sharma
              Container Runtime Eng Bot Container Runtime Eng Bot
              Container Runtime Bugs Bot Container Runtime Bugs Bot
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: