not bad! better than unprotected socket access ;)

INSTALL

sudo curl -sL https://github.com/docker/compose/releases/download/$(curl -is https://github.com/docker/compose/releases/latest|grep Location|awk -F/ '{print $NF}'|grep -Po '[0-9.]+')/docker-compose-Linux-x86_64 -o /usr/local/bin/docker-compose ; sudo chmod +x /usr/local/bin/docker-compose ; docker-compose -v

UPDATE

docker-compose -v ; sudo rm /usr/local/bin/docker-compose ; sudo curl -sL https://github.com/docker/compose/releases/download/$(curl -is https://github.com/docker/compose/releases/latest|grep Location|awk -F/ '{print $NF}'|grep -Po '[0-9.]+')/docker-compose-Linux-x86_64 -o /usr/local/bin/docker-compose ; sudo chmod +x /usr/local/bin/docker-compose ; docker-compose -v

when you are bored doing docker exec -ti foo bash

docker system df
docker system prune
docker system prune --all
docker volume prune

My /var/lib/docker folder was non empty (12GB) event after big cleanup (containers, images, volumes..)

It's a known issue with some layers not removed when you do docker rm -f (force)

Solution : service docker stop; rm -rf /var/lib/docker/*; service docker start

:-/

The nice thing about the command above is that it shows a unified view of all options and takes into consideration any overrides that may have been applied.
To change the value of an option, ExecStart in this case, do the following:

[ec2-user@ip-10-0-46-113 ~]$ sudo systemctl edit docker

This will create the necessary directory structure under /etc/systemd/system/docker.service.dand open an editor (using the default editor configured for the user) to the override file. Add the section below into the editor:

[Service]
ExecStart=
ExecStart=/usr/bin/docker daemon -H tcp://0.0.0.0:2375 -H unix:///var/run/docker.sock

It was necessary to clear out ExecStart using ExecStart= before setting it to the override value. This is only required for some options and most options in the configuration file would not need to be cleared like this