Bug 50058 - docker compose installation broken due to network create problems
docker compose installation broken due to network create problems
Status: NEW
Product: UCS
Classification: Unclassified
Component: App Center
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: App Center maintainers
App Center maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-08-26 17:42 CEST by Felix Botner
Modified: 2019-08-27 10:05 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 1: Cosmetic issue or missing function but workaround exists
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.034
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Botner univentionstaff 2019-08-26 17:42:57 CEST
Seen on my test system (Not in jenkins)

$ univention-app install wekan # this works fine, but 
$ /usr/share/ucs-test/runner -f python /usr/share/ucs-test/80_docker/85_docker_compose

Running command: docker-compose -p ahovq174rh up -d --no-build --no-recreate
Creating network "ahovq174rh_appcenter_net" with the default driver
cannot create network 2c10e9367582a19af7cad46dd69816ab6c444dfd4ab5f2439e797a720e59d171 (br-2c10e9367582): conflicts with network 876522b97a91285470b70e1e2cbc4611b739b08f8aab888082cbae67de72e90b (br-876522b97a91): networks have overlapping IPv4
Command docker-compose -p ahovq174rh up -d --no-build --no-recreate failed with: Creating network "ahovq174rh_appcenter_net" with the default driver
cannot create network 2c10e9367582a19af7cad46dd69816ab6c444dfd4ab5f2439e797a720e59d171 (br-2c10e9367582): conflicts with network 876522b97a91285470b70e1e2cbc4611b739b08f8aab888082cbae67de72e90b (br-876522b97a91): networks have overlapping IPv4 (1)
Creating network "ahovq174rh_appcenter_net" with the default driver
cannot create network 2c10e9367582a19af7cad46dd69816ab6c444dfd4ab5f2439e797a720e59d171 (br-2c10e9367582): conflicts with network 876522b97a91285470b70e1e2cbc4611b739b08f8aab888082cbae67de72e90b (br-876522b97a91): networks have overlapping IPv4
..
Aborting...
Going to remove ahovq174rh (1)
Configuring ahovq174rh=1


$ ifconfig 
br-876522b97a91: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.16.0.1  netmask 255.255.255.0  broadcast 0.0.0.0
        inet6 fe80::42:eaff:fee9:1f1d  prefixlen 64  scopeid 0x20<link>
        ether 02:42:ea:e9:1f:1d  txqueuelen 0  (Ethernet)
        RX packets 34  bytes 2355 (2.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 21  bytes 1755 (1.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.42.1  netmask 255.255.0.0  broadcast 0.0.0.0
        ether 02:42:99:46:34:58  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.200.7.80  netmask 255.255.255.0  broadcast 10.200.7.255
        inet6 fe80::5054:ff:feb0:56d7  prefixlen 64  scopeid 0x20<link>
        ether 52:54:00:b0:56:d7  txqueuelen 1000  (Ethernet)
        RX packets 302812  bytes 508222608 (484.6 MiB)
        RX errors 0  dropped 3191  overruns 0  frame 0
        TX packets 127588  bytes 10115403 (9.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Lokale Schleife)
        RX packets 11062  bytes 4450003 (4.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 11062  bytes 4450003 (4.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth9ef0a06: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::a48e:a1ff:fec9:8bf4  prefixlen 64  scopeid 0x20<link>
        ether a6:8e:a1:c9:8b:f4  txqueuelen 0  (Ethernet)
        RX packets 5306  bytes 691264 (675.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3790  bytes 580476 (566.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vethce22eac: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::430:78ff:fe26:a2ff  prefixlen 64  scopeid 0x20<link>
        ether 06:30:78:26:a2:ff  txqueuelen 0  (Ethernet)
        RX packets 3759  bytes 578001 (564.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5330  bytes 692789 (676.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
Comment 1 Felix Botner univentionstaff 2019-08-26 17:49:54 CEST
# docker-compose.yml from the 80_docker/85_docker_compose test app
networks:
  appcenter_net:
    ipam:
      config:
      - subnet: 172.16.0.0/24
      driver: default

# network from the wekan compose app
$ docker network inspect wekan_appcenter_net 
    ...
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.16.0.0/24"
                }
            ]
# appcenter log
 Running in /var/lib/univention-appcenter/apps/xq7w1uafmt/compose:
  9618 utils                            19-08-26 17:43:45 [    INFO]: Running command: docker-compose -p xq7w1uafmt up -d --no-build --no-recreate
  9618 utils                            19-08-26 17:43:46 [    INFO]: Creating network "xq7w1uafmt_appcenter_net" with the default driver
  9618 utils                            19-08-26 17:43:46 [    INFO]: cannot create network cd6b76878376f12677dc580110e50a7a76555031f4b5bd826f261b2e2d18133e (br-cd6b76878376): conflicts with network 876522b97a91285470b70e1e2cbc4611b739b08f8aab888082cbae67de72e90b (br-876522b97a91): networks have overlapping IPv4
Comment 2 Felix Botner univentionstaff 2019-08-26 17:53:28 CEST
So seems to be a problem when installation multiple compose apps.
Comment 3 Dirk Wiesenthal univentionstaff 2019-08-26 23:18:07 CEST
Yes, I experienced that, too. The problem is that the test uses a local App Center. So wekan is not known (anymore). The App Center does not know of the already used network and tries the first one it thinks is free - the one occupied by wekan.

_Should_ not be seen in real life scenarios. But definitely a problem if it comes to that.
Comment 4 Felix Botner univentionstaff 2019-08-27 10:05:49 CEST
(In reply to Dirk Wiesenthal from comment #3)
> Yes, I experienced that, too. The problem is that the test uses a local App
> Center. So wekan is not known (anymore). The App Center does not know of the
> already used network and tries the first one it thinks is free - the one
> occupied by wekan.
> 
> _Should_ not be seen in real life scenarios. But definitely a problem if it
> comes to that.

ah, ok, so not critical in productive environments (where the appcenter/server settings is never changed)