I have the same issue (on Centos 7 and Docker CE 18.02.0-ce-rc2).
When I do Docker ps -a I see the containers and they show as stopped, but when I try to start them it tells me that they already exist, and attempts to stop and kill them have failed. Have you had any success resolving the issue?
Yes, the issue is happening regardless of whether I use the name or the id (both the short and long hash). And it is happening regardless of whether I use start or restart to try and start the container, and regardless of whether I use stop or kill to stop the container. It appears to be a known issue after upgrading to the latest version of Docker: https://github.com/moby/moby/issues/36145
I begin to experience this issue after updating to Version 18.02.0-ce-rc2-mac51 (22446), I have only the bridge network, no other containers or images but postgres and phppgadmin; after stopping the containers they won’t start again, throwing error
Error response from daemon: container “4a082217387592dc9ef5e675f326ddf33dedf4ead8d52def7ab9b3453073ede4”: already exists
I tried disconnecting the containers from the bridge network, restarting docker and they still won’t start