
Hello, im trying to upgrade from 1.5.11 to 1.6.0 and i got this:
TypeScript
Failed to install Appwrite dockers
time="2025-03-29T23:45:13Z" level=warning msg="volume \"appwrite_appwrite-mariadb\" already exists but was not created by Docker Compose. Use `external: true` to use an existing volume"
time="2025-03-29T23:45:13Z" level=warning msg="volume \"appwrite_appwrite-builds\" already exists but was not created by Docker Compose. Use `external: true` to use an existing volume"
time="2025-03-29T23:45:13Z" level=warning msg="volume \"appwrite_appwrite-functions\" already exists but was not created by Docker Compose. Use `external: true` to use an existing volume"
time="2025-03-29T23:45:13Z" level=warning msg="volume \"appwrite_appwrite-redis\" already exists but was not created by Docker Compose. Use `external: true` to use an existing volume"
time="2025-03-29T23:45:13Z" level=warning msg="volume \"appwrite_appwrite-config\" already exists but was not created by Docker Compose. Use `external: true` to use an existing volume"
time="2025-03-29T23:45:13Z" level=warning msg="volume \"appwrite_appwrite-certificates\" already exists but was not created by Docker Compose. Use `external: true` to use an existing volume"
time="2025-03-29T23:45:13Z" level=warning msg="volume \"appwrite_appwrite-uploads\" already exists but was not created by Docker Compose. Use `external: true` to use an existing volume"
time="2025-03-29T23:45:13Z" level=warning msg="volume \"appwrite_appwrite-cache\" already exists but was not created by Docker Compose. Use `external: true` to use an existing volume"
Container appwrite Stopping
Container appwrite-worker-functions Stopping
Container appwrite-console Recreate
Container appwrite-assistant Recreate
Container appwrite Stopping
Container appwrite-worker-functions Stopped
Container appwrite Stopped
Container openruntimes-executor Recreate
Container appwrite-realtime Stopping
Container appwrite Stopped
Container appwrite-realtime Stopping
Container appwrite-realtime Stopped
Container appwrite-task-maintenance Stopping
Container appwrite-realtime Stopped
Container appwrite-task-scheduler-functions Stopping
Container appwrite-task-maintenance Stopped
Container appwrite-task-scheduler-functions Stopping
Container appwrite-task-scheduler-functions Stopped
Container appwrite-task-scheduler-messages Stopping
Container appwrite-task-scheduler-functions Stopped
Container appwrite-task-scheduler-messages Stopping
Container appwrite-task-scheduler-messages Stopped
Container appwrite-worker-audits Stopping
Container appwrite-task-scheduler-messages Stopped
Container appwrite-worker-audits Stopped
fatal error: concurrent map writes
fatal error: concurrent map writes
goroutine 58 [running]:
github.com/docker/compose/v2/pkg/compose.(*convergence).stopDependentContainers(_, {_, _}, _, {{0x40004b9ed8, 0x7}, {0x0, 0x0, 0x0}, 0x0, ...})
github.com/docker/compose/v2/pkg/compose/convergence.go:235 +0x180```
A lot lines more...
command to update is the same as docs page:
```docker run -it --rm \
--volume /var/run/docker.sock:/var/run/docker.sock \
--volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw \
--entrypoint="upgrade" \
appwrite/appwrite:1.6.0```
I tried to upgrade to 1.6.0 first, to upgrade to 1.6.1 later
Now what to do?
TL;DR
The error "fatal error: concurrent map writes" is occurring when trying to upgrade from 1.5.11 to 1.6.0 in Docker Compose. This issue might be related to conflicting changes in the map structure. One possible solution is to check for any concurrent writes in the codebase that might be causing this issue and resolve them. Additionally, ensure that the Docker volumes are properly managed.Recommended threads
- Error 1.7.4 console team no found
In console when i go to auth, select user, select a membership the url not work. Only work searching the team. It is by the region. project-default- and i get ...
- functions of 1.4 not work on 1.7
Hi, i updated of 1.4 to 1.7 but the function not work i get it error. Do I need to build and deploy the functions again?
- Login Error 500
Hey i have that Problem, i upgrade to the latest version and now i have this error but only on my custom domain not the main domain.. when i try to login
