Docker: Remove all images and containers


You use Docker, but working with it created lots of images and containers. You want to remove all of them to save disk space.


Warning: This will destroy all your images and containers. It will not be possible to restore them!

Run those commands in a shell:
# Delete all containers
sudo docker rm $(docker ps -a -q)
# Delete all images
sudo docker rmi $(docker images -q)

This solution has be proposed by GitHub user @crosbymichael in this issue


Create a global git commit hook

Recently found out about these git hooks and they work flawlessly but my only worry was that I had to copy all my hooks over every repo such that I could use them, which was a pain sometimes.

Then started reading about this so called global git hooks, and found a fix.

Usually the default template library is found at /usr/share/git-core/templates and we are going to use that directory for all our hooks.

1. Enable git templates:

git config --global init.templatedir '/usr/share/git-core/templates/'

This tells git to copy everything in /usr/share/git-core/templates/ to your per-project .git/ directory when you run git init

2. Write your hooks in /usr/share/git-core/templates/hooks.

For example, here’s an update hook (located in /usr/share/git-core/templates/hooks/update):

# Prevent pushing changes to master branch
if [ $USER != "mmphego" ];
  if [ "$1" == refs/heads/master ];
    echo "Manual pushing to this repo is restricted"
    exit 1

4. Make sure the hook is executable.

chmod a+x /usr/share/git-core/templates/hooks/update

5. Re-initialize git in each existing repo you’d like to use this in:

git init

NOTE if you already have a hook defined in your local git repo, this will not overwrite it.

Why am I getting ‘Errno(105): No buffer space available’ when subscribing to multicast addresses?

I have been experiencing multicast subscription when subscribing to more that 20 IP’s via smcroute and python socket module. After vigorous googling I finally found a fix.


Linux OS, limit the number of multicast group memberships that a machine can belong to simultaneously. (A “multicast group membership” indicates that a machine is listening to messages for a specific multicast IP address. In other words, there is a limit on how many multicast IP addresses you can listen to.)

On Linux, in particular, the default limit is relatively small (only 20 on many standard kernels). However, this limit can be configured dynamically.

If you try to subscribe to too many multicast addresses at once, you may run into the error message below:

daemon error: Warn: ADD MEMBERSHIP failed; Errno(105): No buffer space available
daemon error: Warn: ADD MEMBERSHIP failed; Errno(105): No buffer space available
daemon error: Warn: ADD MEMBERSHIP failed; Errno(105): No buffer space available

The “Errno 105” in this message indicates that the errno value returned by the Linux network stack is 105, or ENOBUFS. This return value while adding a multicast address indicates that your machine is trying to be a member of too many multicast groups at the same time.

Network Tuning

Solution is to tune your kernel, backup your current sysclt.conf and replace contents with the ones below.

sudo vim /etc/sysctl.conf

# Bigger buffers (to make 40Gb more practical). These are maximums, but
# the default is unaffected.

# Avoids problems with multicast traffic arriving on non-default interfaces

# Force IGMP v2 (required by CBF switch)

# Increase the ARP cache table
net.ipv4.neigh.default.gc_thresh3 = 4096
net.ipv4.neigh.default.gc_thresh2 = 2048
net.ipv4.neigh.default.gc_thresh1 = 1024

# Increase number of multicast groups permitted
net.ipv4.igmp_max_memberships = 1024

You can reload the configuration file by executing, sudo sysctl -p or by rebooting your system.

Using Git bisect to find out when a bug was introduced!

—-Simplified explanation—-
Here’s how to use git bisect , step-by-step!
Step 1: Find a commit where things were working. …
Step 2: Find a commit where things are not working. …
Step 3 – N: Use git bisect to find the problem commit. …
Step 4: Get back to a working state.
Using Git bisect to figure out when brokenness was introduced

Step by step with code.

git log -4 # find previous working commit
git checkout #hash
git bisect ?

run through previous commits then

git bisect good or bad
git checkout #hash

See link to get more info and better understanding.