Topic :(
```
docker: Error response from daemon: Conflict. The name "/campaign-1862089-j8-ZDTiADHWmMPNE-OyEdg" is already in use by container 8badc1bf19b6e921bff3370fa2ceac283369ffbcb9e24f36ac9010bf08915e7c. You have to remove (or rename) that container to be able to reuse that name.. See 'docker run --help'.
```
Hi Kyle M.,
Looks like your API Sandbox was stuck in a bad state. I've manually killed and restarted it for you, and you shouldn't have any further problems. If this issue crops up again, there may be something unusual going on with one of your API scripts; feel free to post another bug report and reference this thread in case that occurs.
Thanks,
Jeff
Thanks for the help! It's working now.
Is there a way I can force a restart of the docker container from the client side? I tried disabling, removing scripts etc. But the ID seems to be attached to the game itself?
Unfortunately, there is currently no known workaround for a user to resolve this issue. We are still tracking down the underlying cause (whether internal or external), but from what we can tell the error is only resolvable with a manual fix on the backend; in essence, there is a lock on the virtual container that is very rarely not getting removed when the sandbox restarts, and if it is not removed by the normal sandbox shutdown procedure, it must be manually overridden.
As you said, it is tied to the campaign, so you could ostensibly create a copy of the game and everything should then work as normal in that campaign (as it would create a new sandbox), though naturally that comes with the occasional hiccups of using a copied game.
