An internal curl error has occurred while starting runtime! Error Msg: Docker Error: docker: Error response from daemon: Conflict. The container name "/exc4-winner-app-654df2415e477140098d" is already in use by container "54b66ac1fcbeee29358fe8bfe5ce038ddff182ecdca6ba92c1004dc9d0f1ee94". You have to remove (or rename) that container to be able to reuse that name. See 'docker run --help'. \nError Code: 500
Does it ever work or does this error only happen sometimes?
It was running normally before, but yesterday I found that the execution failed.
@joser Are you on cloud?
@Meldiron Could we run into container name conflicts? 👀 Do we check?
Yes, I use Appwrite Cloud
Hmm we have done multiple adjustments to prevent this 🤔 @Drake can you think of a scenario when this could happen?
yes, if there's some problem removing the runtime container: https://github.com/open-runtimes/executor/blob/d379d9ec6dfc3ed05c6c27cb207a210704a6c214/app/http.php#L1218
I don’t need to do anything, can I just wait for you to fix it?
我什么都不需要操作等着你们修复就可以了吗?
Not sure if you can do anything. Probably Appwrite team will apply a fix soon
This runtime method has been deployed for several days, and has not been updated and deployed subsequently. Suddenly this error appeared
这个运行时方式已经部署好几天了,后续一直没有更新部署过。突然就出现这个错误
Recommended threads
- Function executions fail with cURL error...
Appwrite version: 1.8.0 Executor version: 0.11.4 Function runtime: Python 3.12 SELF-HOSTED Function executions that occur at the same moment as the executor's ...
- Build failed
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
- Other DateTime Columns Are Saved Incorre...
When opening a row’s details from the console and editing any field, the timestamps of other DateTime columns are being automatically changed and incorrectly sa...