Failed to start containers.

I'm trying to install Appwrite locally but struck on the subject point. There is no clear error in logs.

<@&1319717958645452800> <@&634618551491100692>

any logs? maybe memory/cpu spike leading to containers crashing?

No logs in Docker

try reset?

can you see docker logs?

Docker logs are as follows: Starting Appwrite installation...

Compose file found, creating backup: docker-compose.yml.1776322413.backup

Env file found, creating backup: .env.1776322413.backup

Detected existing database: mariadb

Starting web installer...

Open your browser at: http://localhost:20080

Press Ctrl+C to cancel installation

those arent docker logs, try going to docker gui and seeing the containers there

or doing docker ps in ur terminal

Sir it is from Docker UI.

I got the same error when fresh installing 1.9.0 and it turns out the executor just wouldn’t work when you brute force past that stage . I’m back on 1.8.1

I’m waiting for bug fixes

on what i see, your showing the logs of the web installer.

Tho we would need the logs of all the others container the web installer create, all thoses others containers are what make Appwrite works.

(if you check the number of container before and after the web installer have been ran, there should be a big difference, even if they are not in a running state, they might have logs or are stuck into a "CREATED" state)

i am still struck. Can someone help me with Installation via AnyDesk please.

did u try this?

<@950583890676940851>

There are 25 total containers when run and none is completed. Error happens when its 0/25.

do u have an ai that can do some kind of analysis? we have very few log points to go off here and need more analytics to conclude something

I have copy paste the full logs in claude but nothing worked

what about a cli tool which can run commands on ur system?

I had the same problem: after the update, the containers would not start again.

Since the new docker-compose.yml had already been generated by the installer, I tried restarting the Docker stack manually. The error already appeared when running:

docker compose down

The error was:

services.appwrite-worker-certificates.environment array items[15,21] must be unique

This means that there were duplicate entries in the environment list of the appwrite-worker-certificates service. In my case, _APP_DB_ADAPTER was listed twice.

Docker Compose refuses to parse/validate the compose file when environment array items are duplicated, so it fails before the containers can even be stopped or started properly.

I removed the duplicate environment entries from the docker-compose.yml, making sure each variable appears only once per service.

After removing the duplicates, the stack started successfully and the update continued.

db adapter issue was fixed, you can wait for a new patch update try removing it urself to workaround 👌

In my case _AP_DB_ADAPTER is duplicate in almost every point. I deleted it manually and just let the one that didn't worked. then installed fresh instance but still has the same duplicate issue.

Apart from this Docker almost consumer 100 percent CPU usage