$ cmgr playtest picoctf/binary-instrumentation-1
cmgr: [ERROR: could not create challenge network (cmgr-2): Error response from daemon: network with name cmgr-2 already exists]
error creating instance: Error response from daemon: network with name cmgr-2 already exists
cmgr: [ERROR: failed to delete build (2): FOREIGN KEY constraint failed]
This can happen if you restart your machine and Docker brings back some containers and networks that you were working with previously, but now cmgr has no recollection of them.
If you're just using Docker for cmgr, the following command is relatively safe, if you're using Docker for other projects as well, you'll want to more carefully stop cmgr containers.
$ docker stop $(docker ps -q)
1222925026a3
15eaaf240e3b
dd5cbb06e859
61e4a6fcd525
Once those containers are stopped, you can prune networks which should take care of the duplicate network issue.
$ docker network prune
WARNING! This will remove all custom networks not used by at least one container.
Are you sure you want to continue? [y/N] y
Deleted Networks:
cmgr-3
cmgr-1
cmgr-4
cmgr-2
cmgr will want you to update again.
$ cmgr update
cmgr: [WARN: skipped removing network (not found): cmgr-2]
cmgr: [WARN: disk quota for picoctf/binary-instrumentation-1 container 'challenge' ignored (disk quotas are not enabled)]
cmgr: [WARN: skipped removing network (not found): cmgr-1]
cmgr: [WARN: disk quota for picoctf/binary-instrumentation-1 container 'challenge' ignored (disk quotas are not enabled)]
Updated:
picoctf/binary-instrumentation-1
And now you can finally playtest.
$ cmgr playtest picoctf/binary-instrumentation-1
challenge information available at: http://localhost:4242/