AIO: waiting for Database container to start - but it looks like it started, no errors

Every 2.0s: sudo docker network inspect bridge                                        cirrus: Fri May 20 15:46:25 2022

[
    {
     	"Name": "bridge",
        "Id": "b0594699383d7d34ae7a456d465e9ba077a88f83c88d02feeb2cd6f0e57d3763",
        "Created": "2022-05-20T15:43:05.660428722+01:00",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.17.0.0/16",
                    "Gateway": "172.17.0.1"
                }
            ]
	},
	"Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
	"ConfigOnly": false,
        "Containers": {},
        "Options": {
            "com.docker.network.bridge.default_bridge": "true",
            "com.docker.network.bridge.enable_icc": "true",
            "com.docker.network.bridge.enable_ip_masquerade": "true",
            "com.docker.network.bridge.host_binding_ipv4": "0.0.0.0",
            "com.docker.network.bridge.name": "docker0",
            "com.docker.network.driver.mtu": "1500"
        },
	"Labels": {}
    }
]

not looking good :frowning:

You did not use the correct command: sudo network inspect nextcloud-aio.

yes! and I needed to do the first setup login screen of the AIO.

now that iā€™ve done that, and with the correct commandā€¦: drum rollā€¦

sudo docker network inspect nextcloud-aio
[
    {
        "Name": "nextcloud-aio",
        "Id": "0c88d69e1c2424284c9525b5790b234b497a049ce1bb1405e1810ba99ff9de6e",
        "Created": "2022-05-20T15:48:19.684403856+01:00",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.19.0.0/16",
                    "Gateway": "172.19.0.1"
                }
            ]
        },
        "Internal": true,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {
            "a468d02164dd1b2a4c8945189d124f668e49f0907a18325982542f2e3f04ab92": {
                "Name": "nextcloud-aio-mastercontainer",
                "EndpointID": "1010344cb8bf4893ea752aa1a6e66f2e8b6a51d90cb6b2fa9bcc5bcbbcec5e83",
                "MacAddress": "02:42:ac:13:00:02",
                "IPv4Address": "172.19.0.2/16",
                "IPv6Address": ""
            },
            "d68a2e966539c0bf76e43fcf32a7300f48bb8d467b447f16a8ab6d52ec68fbac": {
                "Name": "nextcloud-aio-domaincheck",
                "EndpointID": "e9b1536a0f5b3bd2e6a26392f1fb7c3c4715fa9bacf683f66770ab4211534265",
                "MacAddress": "02:42:ac:13:00:03",
                "IPv4Address": "172.19.0.3/16",
                "IPv6Address": ""
            }
        },
        "Options": {
            "com.docker.network.bridge.enable_icc": "true"
        },
        "Labels": {}
    }
]

:crossed_fingers:

looks good to me! Please try the installation again now!

iā€™m tentatively awaitingā€¦ :slight_smile:
i deleted everything in docker, so much to download again.

you could have disabled all optional addons which would have made the download faster :smiley:

1 Like

Does it work now or is it still downloading?

unfortunately, itā€™s the same outcome.

everything is ā€œStartingā€. Database is up, but Nextcloud is waiting for it.

the bridge network does not say internal on it.
the nextcloud-aio network does say internal.

same again here:

sudo docker exec -it nextcloud-aio-nextcloud bash
bash-5.1$ nc -z nextcloud-aio-database 5432; echo $?
1

Hmā€¦ What is the output of sudo network inspect nextcloud-aio?

sudo docker network inspect nextcloud-aio
[
    {
        "Name": "nextcloud-aio",
        "Id": "0c88d69e1c2424284c9525b5790b234b497a049ce1bb1405e1810ba99ff9de6e",
        "Created": "2022-05-20T15:48:19.684403856+01:00",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.19.0.0/16",
                    "Gateway": "172.19.0.1"
                }
            ]
        },
        "Internal": true,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {
            "04be0dee1f444ada7e38b5f293ee0faa87ae94aeeca4681696fdbad16f1a6bb1": {
                "Name": "nextcloud-aio-collabora",
                "EndpointID": "dd22c7863ed9682b0743450d557b1c4c4908d12e39171eb4d262741926ffa45d",
                "MacAddress": "02:42:ac:13:00:03",
                "IPv4Address": "172.19.0.3/16",
                "IPv6Address": ""
            },
            "22518b94cc95163d9a548c5fd530c8d6803107e12307715c1042abc68aef58a2": {
                "Name": "nextcloud-aio-talk",
                "EndpointID": "3e4683b1a90e11a0826f040718423b8c965a44ec0128494c37d8311789ba1541",
                "MacAddress": "02:42:ac:13:00:05",
                "IPv4Address": "172.19.0.5/16",
                "IPv6Address": ""
            },
            "298f11b2ddfce8dc082eca350030ac669b335f79211fffa5e90e1cd3c3d237b9": {
                "Name": "nextcloud-aio-apache",
                "EndpointID": "ce022e8741539b44e173227246ef0a6fc7321a3f0507178efa92311a77243b2f",
                "MacAddress": "02:42:ac:13:00:09",
                "IPv4Address": "172.19.0.9/16",
                "IPv6Address": ""
            },
            "a468d02164dd1b2a4c8945189d124f668e49f0907a18325982542f2e3f04ab92": {
                "Name": "nextcloud-aio-mastercontainer",
                "EndpointID": "1010344cb8bf4893ea752aa1a6e66f2e8b6a51d90cb6b2fa9bcc5bcbbcec5e83",
                "MacAddress": "02:42:ac:13:00:02",
                "IPv4Address": "172.19.0.2/16",
                "IPv6Address": ""
            },
            "c2665a9220c93d23973598ed3de85a251092c19f7296f4b0e3e6b6b7311b9396": {
                "Name": "nextcloud-aio-clamav",
                "EndpointID": "7b8c00c7a42d9eec1af2a356982932b4eaea2ec509b0af2aa4b3098a48663096",
                "MacAddress": "02:42:ac:13:00:04",
                "IPv4Address": "172.19.0.4/16",
                "IPv6Address": ""
            },
            "d0efe4fb7613e8ed7c9432f786e1405b4d0adfb0359bf9e9d97465a40ee3f7c2": {
                "Name": "nextcloud-aio-redis",
                "EndpointID": "621fe1eb4fe78c28940ee372f950d10ba3bb02ca9f0b90bf9017eed5c55951f0",
                "MacAddress": "02:42:ac:13:00:07",
                "IPv4Address": "172.19.0.7/16",
                "IPv6Address": ""
            },
            "d548bc6a83bc846c99d31cd2fa1923235a7e61467068280835b6ebff8197bc11": {
                "Name": "nextcloud-aio-nextcloud",
                "EndpointID": "0d90cb069463e856d36fde66ea1ae2c77c4d67d228d2a379e9761b8a0347453d",
                "MacAddress": "02:42:ac:13:00:08",
                "IPv4Address": "172.19.0.8/16",
                "IPv6Address": ""
            },
            "ebb7764b3694b105293ca4e7bf8ada1ed3d764d0226a7c0e7bba935d3621c913": {
                "Name": "nextcloud-aio-database",
                "EndpointID": "a1d843824cd7f77721a25cb1d2e37499218b8c9480087dfc4ac8b062ca4865f7",
                "MacAddress": "02:42:ac:13:00:06",
                "IPv4Address": "172.19.0.6/16",
                "IPv6Address": ""
            }
        },
        "Options": {
            "com.docker.network.bridge.enable_icc": "true"
        },
        "Labels": {}
    }
]

Hmā€¦ this looks goodā€¦

Too bad! I thought we would have found the issue and a fix for itā€¦

I still think that it must be something with the internal networking but for me it works correctlyā€¦

looking back through our conversation, the nextcloud-aio was originally Internal: true
so if the bridge does not need to be internal, then I guess we were looking at the wrong bit.

do you have ufw enabled on your server?

no, I donā€™t. is that a ubuntu thing?
iā€™m using Fedora, it has firewalld. Which is enabled, and I believe docker is configuring the ports with it directly.

if i disable firewalld, the docker container wonā€™t start.

All right, then I donā€™t have more ideas what we could try unfortunately :confused:

As I said, it looks like a networking/firewall issue.

My last idea would be trying to run it manually: all-in-one/latest.yml at main Ā· nextcloud/all-in-one Ā· GitHub And then see which network configs are differently (assuming running it manually works on your serverā€¦)

Sorry, I sent the wrong link. The link to the documentation on running it manually is this one: all-in-one/manual-install at main Ā· nextcloud/all-in-one Ā· GitHub

1 Like

Commenting because this is the issue Iā€™m having on a similar OS (Fedora 35, though not in a VM).

I followed through the same steps here and still have the same issue with the database log saying it has started but the nextcloud log repeating that itā€™s waiting for the DB.

Can I offer any files or outputs?

Hello, I fear it simply does not work on your server currently. Thus your only option seems to be AIO: waiting for Database container to start - but it looks like it started, no errors - #35 by szaimen currentlyā€¦

Worth a shot, youā€™ve answered my questions twice, once in the wrong thread. Thank you for all the assistance and patience!

I think I might try a VM of something other than Fedora to get around my OS.

Docker currently does not cooperate with the nftables backend. It currently side-steps firewalld by injecting its own rules in iptables ahead of firewalldā€™s rules. However, with the nftables backend firewalldā€™s rule will still be evaluated. Netfilter in the kernel will call iptables, then nftables for the same packet. This means firewalld/nftables is likely to drop the packet even if docker has iptables rules to ACCEPT.

https://fedoraproject.org/wiki/Changes/firewalld_default_to_nftables

Maybe this is worth a try?