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

No option to specify static IP during podman network connect command #10277

Closed
psaini79 opened this issue May 8, 2021 · 1 comment
Closed
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@psaini79
Copy link

psaini79 commented May 8, 2021

/kind bug

Description
Unable to assign static IPs with podman network connect command.

Steps to reproduce the issue:

  1. Create a bridge

  2. Create a container

  3. Connect a network to a bridge with the static IP

Describe the results you received:
Network failed to connect with the static IP.

[root@podman-test-server opc]# podman network connect test_nw_pub1 --ip 172.16.1.150 cnt1
Error: unknown flag: --ip

Describe the results you expected:
Podman must be able to assign static IP.

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

Version:      2.2.1
API Version:  2
Go Version:   go1.14.12
Built:        Fri Feb 19 11:46:00 2021
OS/Arch:      linux/amd64

Output of podman info --debug:

[root@podman-test-server opc]# podman info --debug
host:
  arch: amd64
  buildahVersion: 1.18.0
  cgroupManager: systemd
  cgroupVersion: v1
  conmon:
    package: conmon-2.0.22-3.module+el8.3.1+9659+c1901784.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.22, commit: 3ef8df793032fc21d5db1f32c0b3e5a73998381c'
  cpus: 4
  distribution:
    distribution: '"ol"'
    version: "8.3"
  eventLogger: file
  hostname: podman-test-server
  idMappings:
    gidmap: null
    uidmap: null
  kernel: 5.4.17-2036.102.0.2.el8uek.x86_64
  linkmode: dynamic
  memFree: 23222333440
  memTotal: 24651005952
  ociRuntime:
    name: runc
    package: runc-1.0.0-70.rc92.module+el8.3.1+9659+c1901784.x86_64
    path: /usr/bin/runc
    version: 'runc version spec: 1.0.2-dev'
  os: linux
  remoteSocket:
    path: /run/podman/podman.sock
  rootless: false
  slirp4netns:
    executable: ""
    package: ""
    version: ""
  swapFree: 4294963200
  swapTotal: 4294963200
  uptime: 14h 17m 16.53s (Approximately 0.58 days)
registries:
  search:
  - container-registry.oracle.com
  - docker.io
  - registry.fedoraproject.org
  - quay.io
  - registry.centos.org
store:
  configFile: /etc/containers/storage.conf
  containerStore:
    number: 1
    paused: 0
    running: 0
    stopped: 1
  graphDriverName: overlay
  graphOptions:
    overlay.mountopt: nodev,metacopy=on
  graphRoot: /var/lib/containers/storage
  graphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "true"
  imageStore:
    number: 11
  runRoot: /var/run/containers/storage
  volumePath: /var/lib/containers/storage/volumes
version:
  APIVersion: "2"
  Built: 1613735160
  BuiltTime: Fri Feb 19 11:46:00 2021
  GitCommit: ""
  GoVersion: go1.14.12
  OsArch: linux/amd64
  Version: 2.2.1

Package info (e.g. output of rpm -q podman or apt list podman):

podman-2.2.1-7.0.1.module+el8.3.1+9659+c1901784.x86_64

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)

Yes

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

@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label May 8, 2021
@Luap99
Copy link
Member

Luap99 commented May 8, 2021

Dup of #9883

@Luap99 Luap99 closed this as completed May 8, 2021
@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 22, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

2 participants