Error name is already in use by container
Why do I get the error below when I execute one of the functions and how can I fix it?
An internal curl error has occurred while starting runtime! Error Msg: Docker Error: docker: Error response from daemon: Conflict. The container name "/appwrite-executor-dev-brd-651a6853601e29912cc7" is already in use by container "32b06a08d0a1741056160f0d9fed07dbdc58f0dbdbace0bac2a170788f0b2fdb". You have to remove (or rename) that container to be able to reuse that name. See 'docker run --help'. \nError Code: 500
@Aditya Oberai can you take a look at this?
@develocode777 can you share more about any steps that led to the error? Were you trying to redeploy and execute a function or was this the first time?
Also, what version of Appwrite are you self-hosting?
@Aditya Oberai we did the upgrade to 1.4.5, then run migration and then changed _APP_WORKER_PER_CORE to 11
if we restart appwrite the error goes away but it comes back after a while
Can you try this command in your appwrite installation directory?
docker logs openruntimes-executor
Also
docker logs appwrite-worker-functions
Let's check the logs once and see if we get more details
@Aditya Oberai here
cc: @Meldiron
Hey there 👋 Error you mentioned in your first message could be reasonable after migration - some containers might have nto been cleaned up properly. That caused missmatch between docker state, and executor state. Restart is a good solution to that, as it should not be happening anymore.
Regarding function worker, logs seems good to me.
Regarding executor, I can only see issues with build containers, most likely causing realtime logs to not work (but rest of build works fine, so you are not facing any significant issue).
Can you confirm with me what issue are you facing currently? Do you still see errors when trying to execute your function?
@Meldiron Hello, we are getting the same error even after restarting a few times, we even restored the same .env file before we made those changes
but now the error is from a different function
we've upgraded to 1.4.7, run migrate and restarted and it seems to be ok now
@Meldiron after a fresh install of version 1.4.5 I get this error again randomly on functions
some work some don't
we had to go to version 1.4.5 because next versions have an issue with high cpu on appwrite-worker-deletes
btw, this should be resolved in the latest patch
