Jump to navigation Jump to search


All Docker commands below need to be prepended by "sudo docker"

Location of Image Files

The contents of the /var/lib/docker directory vary depending on the driver Docker is using for storage. By default this will be aufs but can fall back to overlay, overlay2, btrfs, devicemapper or zfs depending on your kernel support. In most places this will be aufs but the RedHats went with devicemapper.

Basic Commands

  • images
  • rmi (or rmi -f if simple image delete fails)
  • ps -a
  • container ls
  • stop [ -t delay ] my_container

The docker system prune command will remove all stopped containers, all dangling images, and all unused networks:

  • system prune

System Configuration

After configuration changes, a restart is usually needed:

sudo service docker restart
# or, the daemon can be started explicitely as follows:
sudo nohup docker daemon -H tcp:// -H unix:///var/run/docker.sock &

In firewall/restricted environments, the following needs to be in the /etc/docker/daemon.json file (put in your specific DNS):


This should work, but in some other cases the file /etc/default/docker may need to be tweaked, specifically the OPTS.

Pulling from the Repo

pull mediawiki


run --name some-mediawiki -p 8080:80 -d mediawiki
run --name some-mariadb -e MYSQL_ROOT_PASSWORD=foobar -p 3306:3306 -d mariadb/server

To make data managed in the container persistent between runs of the image one may use the "volume" option e.g.

....  -v /my/chosen/folder:/docker/container/inner/location ...


journalctl -u docker.service


docker apache image mod_wsgi python 3

The Host IP

/sbin/ip route|awk '/default/ { print $3 }'