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

Docker Compose support setting static IP #10240

Closed
jose-pr opened this issue May 6, 2021 · 1 comment · Fixed by #10246
Closed

Docker Compose support setting static IP #10240

jose-pr opened this issue May 6, 2021 · 1 comment · Fixed by #10246
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

@jose-pr
Copy link

jose-pr commented May 6, 2021

/kind bug

Description

Static IP configuration in a docker-compose file not setting the ip.

Steps to reproduce the issue:

version: "3.2"
   
services:
  emby:
    image: docker.io/emby/embyserver:latest 
    networks:
      default:
        ipv4_address: 10.7.88.2
    environment:
      UID: 0
      GUID: 0
networks:
  default:
    external:
        name: podman

docker-compose up
3.

 podman inspect emby_emby_1 | grep -i ip
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
        "IPAddress": "10.7.88.9",
        "IPPrefixLen": 24,
        "IPv6Gateway": "",
        "GlobalIPv6Address": "",
        "GlobalIPv6PrefixLen": 0,
        "IPAMConfig": null,

Describe the results you expected:

I expected the IPAddress to be 10.7.88.2

Output of podman version:

Version:      3.1.2
API Version:  3.1.2
Go Version:   go1.16
Built:        Thu Apr 22 09:11:28 2021
OS/Arch:      linux/amd64```

**Output of `podman info --debug`:**

host:
arch: amd64
buildahVersion: 1.20.1
cgroupManager: systemd
cgroupVersion: v2
conmon:
package: conmon-2.0.27-2.fc34.x86_64
path: /usr/bin/conmon
version: 'conmon version 2.0.27, commit: '
cpus: 8
distribution:
distribution: fedora
version: "34"
eventLogger: journald
idMappings:
gidmap: null
uidmap: null
kernel: 5.11.12-300.fc34.x86_64
linkmode: dynamic
memFree: 272363520
memTotal: 33620488192
ociRuntime:
name: crun
package: crun-0.19.1-2.fc34.x86_64
path: /usr/bin/crun
version: |-
crun version 0.19.1
commit: 1535fedf0b83fb898d449f9680000f729ba719f5
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
os: linux
remoteSocket:
exists: true
path: /run/podman/podman.sock
security:
apparmorEnabled: false
capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
rootless: false
seccompEnabled: true
selinuxEnabled: true
slirp4netns:
executable: ""
package: ""
version: ""
swapFree: 25629548544
swapTotal: 25768747008
uptime: 1h 39m 46.44s (Approximately 0.04 days)
registries:
search:

  • registry.fedoraproject.org
  • registry.access.redhat.com
  • docker.io
  • quay.io
    store:
    configFile: /etc/containers/storage.conf
    containerStore:
    number: 7
    paused: 0
    running: 1
    stopped: 6
    graphDriverName: overlay
    graphOptions:
    overlay.mountopt: nodev,metacopy=on
    graphRoot: /data/containers/storage
    graphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "true"
    imageStore:
    number: 10
    runRoot: /var/run/containers/storage
    volumePath: /data/containers/storage/volumes
    version:
    APIVersion: 3.1.2
    Built: 1619097088
    BuiltTime: Thu Apr 22 09:11:28 2021
    GitCommit: ""
    GoVersion: go1.16
    OsArch: linux/amd64
    Version: 3.1.2

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

podman-3.1.2-1.fc34.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/No

**Additional environment details (AWS, VirtualBox, physical, etc.):**
@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label May 6, 2021
@Luap99
Copy link
Member

Luap99 commented May 6, 2021

I think this requires #9883

@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

Successfully merging a pull request may close this issue.

3 participants