Cant run docker compose up -d

appwrite git:(main) ✗ docker-compose up -d
[+] Running 11/1
⠿ Network appwrite_appwrite Created 0.0s
[+] Running 12/11te_runtimes Created 0.0s
⠿ Network appwrite_appwrite Created 0.0s
⠿ Network appwrite_runtimes Created 0.0s
⠿ Network appwrite_gateway Created 0.0s
...
...
⠿ Volume "appwrite_appwrite-cache" Created 0.0s
⠿ Volume "appwrite_appwrite-functions" Create... 0.0s
⠿ Volume "appwrite_appwrite-redis" Created 0.0s
⠿ Volume "appwrite_appwrite-builds" Created 0.0s
⠿ Volume "appwrite_appwrite-certificates" Cre... 0.0s
⠋ Container appwrite-telegraf Creating 0.0s
⠋ Container appwrite-influxdb Creating 0.0s
⠋ Container appwrite-redis Creating 0.0s
⠋ Container appwrite-mariadb Creating 0.0s
Error response from daemon: Conflict. The container name "/appwrite-redis" is already in use by container "0be6aaf59a903dea89c3687e662450f0bccf568f80c97c36e3af90312e269395". You have to remove (or rename) that container to be able to reuse that name.

It seems like you already have appwrite-redis run before.

Run

And

And share the results.

You'll need to remove all old containers

Is this production or development?

development; but after setting up db's, functions, etc

If I try restarting containers, I get the error:

appwrite git:(main) ✗ docker compose start
service "influxdb" has no container to start

But influxdb, redis, etc all clearly have created containers...

Okay,
Use it on your own risk (maybe after backup)
This command will remove and delete all of you containers, it won't delete volumes, etc.

Then, you can run

docker-compose up -d 

worked like a charm -- why did these containers need to be nuked though?

Docker compose needs to run all the serices as a whole, from some reason the appwrite-redis wasn't attached, then the best is to get rid of all of them.

And just restart the compose file.

As the data is persisted into Docker volumes.

got it; I ran into this issue earlier trying to get a function to work and just nuked everything since I wasn't too far into a project.

I noticed that the name of the parent folder of the docker-compose file is getting prepended to a lot of the services/volumes. I'm gathering that this is pretty important?

What you mean prepended can you show how?

there was a issue thread that explained this -- and why the parent folder should be named appwrite. I had it named backend before, all of the volume names were prepended with backend_*

That's how docker work

It's the expected behavior

And for you it will stay the same name as in the docker compose