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 .
×
This post has been closed. You can still view previous posts, but you can't post any new replies.

API Script error received.

I have made no changes to my scripts since last playing yet when I went to review the scripts I received the following error: docker: Error response from daemon: Conflict. The name "/campaign-3901732-8gjm1MnNARvnpLWdTuz7zQ" is already in use by container 2c3d9e50008ee978f95a544dccb02467396d3dbf18f9814fd9f43dff6519d22a. You have to remove (or rename) that container to be able to reuse that name.. See 'docker run --help'.
Yeah I currently have and likewise I've made no changes. It worked 2½ hours ago, now I get this error code. docker: Error response from daemon: open /var/lib/docker/containers/ceb0e01fa00a52790342b5eeccdd8958f0197ae0d28a9b11c5971c7fb9ca4337/hosts: no space left on device. I have no idea on how to fix it
Yep.  realized i wasn't getting some of my API commands, and I was getting something like Kasper's error.  I disabled the 13th age script and restarted, that led to Keith's error.
I am having the same conflict issue as Keith. Spinning up new sandbox... docker: Error response from daemon: Conflict. The name "/campaign-3926397-0oYTZAaNG77Rdd92St_6bQ" is already in use by container 6e4dc447b5eb89388fa3c82ec267c31e77390ace8abed91fc3ddb3054cf4f02a. You have to remove (or rename) that container to be able to reuse that name.. See 'docker run --help'.
Hi. Yeah, same. Receiving both errors. Disabled everything, re-saved everything, removed scripts, added scripts. That's about all the kung-fu I can manage. Thanks. Byron.
1542232463
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
Thanks folks, I have alerted the dev team that there is an issue. There is another thread where this error is being reported . I am going to close this thread and you can follow it there so that we can consolidate the response. I'll copy your reports over to it momentarily.