Error response from daemon: Container xxxxxx is already active

If you face this issue where it said "Error response from daemon: Container xxxxxx is already active", and your Container is unable to start, the only way it seems to work for me, is to do the following

sudo service docker restart

and the so call 'active' container will starts itself, using other command fails to start this baby up.

Share
Livedrive Simple, Secure Online Backup Increase sales with social commerce at BigCommerce. Learn More!

Leave a Comment

eighteen − seven =