[rootful/rootless] Can't setup appwriter compose, because network timeout, resolve

[DevDorrejo]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

Hello, i am trying to setup appwrite using podman compose, but when all the container is up, is giving me errors related to each container can't see each one, timeout or can't get a port.

Steps to reproduce the issue:

1. run this script on a rootless user https://pastebin.com/HptZer17, this on rootful: https://pastebin.com/LeVfEsCr

2. do docker-compose up

3. let the container finish boot up.

Describe the results you received: Neither of the containers can get network (local) access and create timeout, fail on getaddrinfo.

Using the cni troubleshooting on rootles create a issue, because the network created by the compose

docker-compose up --remove-orphans
Starting appwrite-redis ... 
appwrite-telegraf is up-to-date
appwrite-mariadb is up-to-date
Starting appwrite-redis ... error

ERROR: for appwrite-redis  container 24353d0a9dd5708124a53aad4bca4770f82d94c4fdf04b13b3cece7cdd6c0b8b is already connected to CNI network "appwrite_appwrite": network already exists

ERROR: for redis  container 24353d0a9dd5708124a53aad4bca4770f82d94c4fdf04b13b3cece7cdd6c0b8b is already connected to CNI network "appwrite_appwrite": network already exists
ERROR: Encountered errors while bringing up the project.

if using docker not have issue or rootful.

Describe the results you expected: successful use of the service

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

Output of podman version:

podman version 3.2.2

Output of podman info --debug:

host:
  arch: amd64
  buildahVersion: 1.21.0
  cgroupControllers: []
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon-2.0.27-1.3.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.27, commit: unknown'
  cpus: 4
  distribution:
    distribution: '"opensuse-tumbleweed"'
    version: "20210711"
  eventLogger: journald
  hostname: TW-Labs
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 20000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 20000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  kernel: 5.13.0-1-default
  linkmode: dynamic
  memFree: 4327460864
  memTotal: 8332414976
  ociRuntime:
    name: runc
    package: runc-1.0.0-1.1.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0
      spec: 1.0.2-dev
      go: go1.13.15
      libseccomp: 2.5.1
  os: linux
  remoteSocket:
    exists: true
    path: /run/user/20000/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_AUDIT_WRITE,CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_MKNOD,CAP_NET_BIND_SERVICE,CAP_NET_RAW,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /etc/containers/seccomp.json
    selinuxEnabled: false
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.1.11-1.1.x86_64
    version: |-
      slirp4netns version 1.1.11
      commit: unknown
      libslirp: 4.4.0
      SLIRP_CONFIG_VERSION_MAX: 3
      libseccomp: 2.5.1
  swapFree: 0
  swapTotal: 0
  uptime: 56m 22.38s
registries:
  search:
  - registry.opensuse.org
  - docker.io
  - quay.io
store:
  configFile: /opt/appwriter/.config/containers/storage.conf
  containerStore:
    number: 0
    paused: 0
    running: 0
    stopped: 0
  graphDriverName: btrfs
  graphOptions: {}
  graphRoot: /opt/appwriter/.local/share/containers/storage
  graphStatus:
    Build Version: 'Btrfs v5.12.1 '
    Library Version: "102"
  imageStore:
    number: 30
  runRoot: /run/user/20000/containers
  volumePath: /opt/appwriter/.local/share/containers/storage/volumes
version:
  APIVersion: 3.2.2
  Built: 1624752000
  BuiltTime: Sat Jun 26 20:00:00 2021
  GitCommit: ""
  GoVersion: go1.13.15
  OsArch: linux/amd64
  Version: 3.2.2

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

podman-3.2.2-1.1.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.): Libvirtd/KVM + Qemu: openSUSe TW 20210711

[rhatdan]

Podman and podman-compose are two different projects. This might be an issue in the way podman-compose is setting up the network. Why do you think this is a Podman issue?

[DevDorrejo]

Podman and podman-compose are two different projects. This might be an issue in the way podman-compose is setting up the network. Why do you think this is a Podman issue?

didn't know that is unrelated to the main proyect, can you give me where i have to post this?

thank you.

[DevDorrejo]

i found, it thanks.