podman: `podman create --mac-address` doesn't work

/kind bug

Description

The --mac-address switch to podman create/podman run doesn’t work.

Steps to reproduce the issue:

# podman run --rm -it --mac-address=02:23:45:67:89:ab registry.fedoraproject.org/fedora-minimal:28 cat /sys/class/net/eth0/address
0a:58:0a:58:01:5a

Describe the results you received:

An automatically-assigned MAC address.

Describe the results you expected:

The MAC address I specifiied in the argument.

Output of podman version:

Version:       0.7.2
Go Version:    go1.10.3
OS/Arch:       linux/amd64

Output of podman info:

Output of `podman info` 
host:
  MemFree: 8406614016
  MemTotal: 16652193792
  SwapFree: 8398041088
  SwapTotal: 8398041088
  arch: amd64
  cpus: 4
  hostname: trabajo.itz.uni-halle.de
  kernel: 4.17.6-200.fc28.x86_64
  os: linux
  uptime: 20m 9.95s
insecure registries:
  registries:
  - trabajo.itz.uni-halle.de:5000
registries:
  registries:
  - trabajo.itz.uni-halle.de:5000
  - registry.fedoraproject.org
  - docker.io
store:
  ContainerStore:
    number: 0
  GraphDriverName: vfs
  GraphOptions: []
  GraphRoot: /home/ajaam/.local/share/containers/storage
  GraphStatus: {}
  ImageStore:
    number: 1
  RunRoot: /run/user/29574/run

Additional environment details (AWS, VirtualBox, physical, etc.):

Contents of /etc/cni/net.d/87-podman-bridge.conflist 
{
    "cniVersion": "0.3.0",
    "name": "podman",
    "plugins": [
      {
        "type": "bridge",
        "bridge": "cni0",
        "isGateway": true,
        "ipMasq": true,
        "ipam": {
            "type": "host-local",
            "subnet": "10.88.0.0/16",
            "routes": [
                { "dst": "0.0.0.0/0" }
            ]
        }
      },
      {
        "type": "portmap",
        "capabilities": {
          "portMappings": true
        }
      }
    ]
}

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 49 (28 by maintainers)

Commits related to this issue

Most upvoted comments

Sure, I think this is a good candidate for 1.5.

On Thu, Aug 1, 2019, 05:30 Daniel J Walsh notifications@github.com wrote:

@mheon https://github.com/mheon Is this something we can get in for podman 1.5 along with IPV6 support? Seems like a nice feature to add.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/containers/libpod/issues/1136?email_source=notifications&email_token=AB3AOCHAICGFQDT2UYMAGCLQCKUJ5A5CNFSM4FLMURAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3J7BTQ#issuecomment-517206222, or mute the thread https://github.com/notifications/unsubscribe-auth/AB3AOCG3SIPOJQJJOLCXVQLQCKUJ5ANCNFSM4FLMURAA .

+3
mheon on Aug 1, 2019

But its acually still a issue for me, because I didnt acually fuck up. It was this mac that sendt a request to my dhcp server: 0a:dd:5b:ce:23:d1

Why? how am I suppose to set static IPs in pfsense then? whats happening?

+1
leier69 on Feb 3, 2020

Fuck. They match up…

+1
leier69 on Feb 3, 2020

I could not resist to play with a little bit (not compiled nor tested): https://github.com/filak-sap/libpod/commit/9abe0ad1228140e0690595a5f762f00ed49b2bb9

+1
filak-sap on Sep 17, 2019
Read more comments on GitHub
← podman: podman compose it not working on some projects on macOS
podman: Podman creates images that cannot be removed →