Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account
This post has been closed. You can still view previous posts, but you can't post any new replies.

Docker: error response from daemon, API scripts won't work.

1579894094

Edited 1579894164
docker: Error response from daemon: Conflict. The name "/campaign-5407882-7B0ex-MBDmG1CP8tsc59yw" is already in use by container 67be443ae0d5767b2c324967a26eba61619e6ce8fff2ab17b91ef1b44e7b7814. You have to remove (or rename) that container to be able to reuse that name.. See 'docker run --help'. Getting this error on my Tyrant's Grasp campaign. I use a fair bit of api for that one so this is frustrating, especially since my next game is tomorrow. Don't know what happened or why. I've disabled all my custom scripts, no dice. Restarted api. No dice. Exited out of roll20. No dice. Not sure how to fix this if I even can.
I just came here to post the same issue with the same steps you listed above. I don't think it's on our end.
However, the exact same scripts are working in my other game that I just checked.
1579895338

Edited 1579895395
That too is my problem. My Zeitgeist game is working just fine with the same scripts. The good news is I'm doing a conversion to 4e so I have non-map roll20 related prep to work on so I'm not hamstrung by this but I wanted to try out a new door knocker api script I read.
Hey all -  Apologies for any trouble with this! Our API servers needed a quick tweak and restart. However, this issue should be resolved now. Would you mind re-testing the API on any affected games and letting me know the results, please? Thank you for your patience!
I did a manual restart of my API on my game and it's working now, thanks!
Working for me now as well thanks!
I am still having that same problem. docker: Error response from daemon: Conflict. The name "/campaign-5356284-1phbWMr0H6_JjcDBqbbOrQ" is already in use by container 202bc2b2b8b0d8794b4047f06017f9129059d189f9df8e4fca92c4fc2e7dfd02. You have to remove (or rename) that container to be able to reuse that name.. See 'docker run --help'.
I am also still having this issue on one campaign (Trial of Blood: <a href="https://app.roll20.net/campaigns/details/1247394/the-trial-of-blood" rel="nofollow">https://app.roll20.net/campaigns/details/1247394/the-trial-of-blood</a>) I was hoping to prepare a bunch of stuff tonight but I need the api in order to do that.&nbsp; Hopefully it resolves sooner than later. docker: Error response from daemon: Conflict. The name "/campaign-1247394-WvNLWQu-JVwMQxxDXMYRfw" is already in use by container 21dc9f59567f01394f0bd19bfafcd04941a190b8f35c1027cb7909bf7d610612.
Just tested on my side and I'm getting the same below error. Star Wars FFG Dice Roller API docker: Error response from daemon: Conflict. The name "/campaign-1884237-hvPHxMJnYcI1tUqmFcd_SA" is already in use by container 0153723d3bae4b3c63df877765dfdc475102921c38ad7f6887dd25dbdbfb7228. You have to remove (or rename) that container to be able to reuse that name..
Still having the same issue.&nbsp; I really hope this is cleared up by tonight. Andy R. said: I am also still having this issue on one campaign (Trial of Blood: <a href="https://app.roll20.net/campaigns/details/1247394/the-trial-of-blood" rel="nofollow">https://app.roll20.net/campaigns/details/1247394/the-trial-of-blood</a>) I was hoping to prepare a bunch of stuff tonight but I need the api in order to do that.&nbsp; Hopefully it resolves sooner than later. docker: Error response from daemon: Conflict. The name "/campaign-1247394-WvNLWQu-JVwMQxxDXMYRfw" is already in use by container 21dc9f59567f01394f0bd19bfafcd04941a190b8f35c1027cb7909bf7d610612.
Hello all -&nbsp; Apologies for the issues and delay in resolution! It looks like there were still a few isolated API servers that were having some trouble. However, we have adjusted those servers, restarted them, and implemented a solution to prevent any future occurrences. Would you all mind retesting the API servers in your games now and letting me know the results, please? Make sure to restart your API sandbox during this testing process. Again, we really appreciate your patience as we work through this!
For to moment it seems my API is functioning. Thank you!
Hey everyone -&nbsp; For better report consolidation, please refer to and utilize&nbsp; this post for further communication regarding this issue . As a result, I'm going to go ahead and close this post. We appreciate your patience!&nbsp;