An internal curl error has occurred while starting runtime! Error Msg: Docker Error: docker: Error response from daemon: Conflict. The container name "/exc5-65c5df06933e47ebdec4-65db2b1e57482e06673b" is already in use by container "af988d3c2da9426f5f2a4444cb0fcc723676efa41a671d4aded842d0f47cf3ee". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.
\nError Code: 500
for now, best if you redeployed
ohh I see I will try
thanks steve the function is working right now
[SOLVED] My CLoud function suddenly not working
The underlying problem is the executor thinks the runtime container doesn't exist but it does. We keep track of the active runtimes in memory table but for some reason there's an error adding the entry in the table
Recommended threads
- Error: Timed out waiting for runtime
I am trying to call a function on appwrite cloud (python 3.9), but I keep getting the above error (Timed out waiting for runtime) saying it timed out after 30 s...
- Random function timeouts
Sometimes my function runs without issue and I can see my logs in the Logs tab on cloud.appwrite.io. Other times, the function fails with a 500 status code, the...
- [SOLVED] Get Relations when using Tables...
Hi there, I have a table containing a relation column with a one-to-many relationship to another table. When Using TablesDB.GetRow in "node-appwrite" i get all ...