Docker: only commit to image if service URL returns HTTP code 200 (OK)

Docker: only commit to image if service URL returns HTTP code 200 (OK)

Safe backup image overwriting #2

With docker, there are several ways to backup your data or entire containers; one of those ways is to commit to an image, which can later be used to fire a container with the exact same contents the source container had when that image was created.

But if for some reason the container gone bad, you don't want to overwrite that image with its contents. If this is a service with a HTTP endpoint, one way is to check if its base URL returns HTTP code 200 (OK); if it does, everything is ok and we can go ahead and replace last image with current contents one:

#!/bin/bash
ret=$(curl -I -s "$2" -o /dev/null -w "%{http_code}\n")
((ret==200)) && docker commit $1 $1_fb

In  this case, I'm creating an image with the name of the running container plus a "_fb" suffix to identify that it's the one with my contents.

Call it via

./<script name>.sh <container name or id> <base URL>

If you want to make some basic clean-up, delete the untagged images by adding to the script

docker rmi $(docker images -a | grep "^<none>" | awk '{print $3}')

Enjoy!

Docker: only commit to image if container running

Docker: only commit to image if container running

Safe backup image overwriting #1

With docker, there are several ways to backup your data or entire containers; one of those ways is to commit to an image, which can later be used to fire a container with the exact same contents the source container had when that image was created.

But if for some reason the container gone bad, you don't want to overwrite that image with its contents. One way is to check if the container is running: if running then odds are that everything is ok, and we can go ahead and replace last image with current contents one:

#!/bin/bash
if $(docker inspect -f {{.State.Running}} $1);  
then
     docker commit $1 $1_fb
fi

In  this case, I'm creating an image with the name of the running container plus a "_fb" suffix to identify that it's the one with my contents.

Call it via

./<script name>.sh <container name or id>

If you want to make some basic clean-up, delete the untagged images by adding to the script

docker rmi $(docker images -a | grep "^<none>" | awk '{print $3}')

Enjoy! 

Simple yet smart backup script for ElasticSearch Data

Backup script for ElasticSearch Data

Simple yet smart

If you have a ES endpoint that for some reason got a severe DELETE, and you only noticed it a couple of days later (ok, we aren't talking about any production deployment, of course), here's a little script that checks if current backup file size is bigger than 50MB, and only replaces last backup if true. First it compares if it's bigger than current bigger one:

#!/bin/bash 

cd /DATA/backups 

tar cvfz ESdata-today.tar.gz ../ESdata/ 

today=$(stat -c %s ESdata-today.tar.gz) 

prev=$(stat -c %s ESdataBigger.tar.gz) 

if [ "$today" -gt "$prev" ];
then
mv ESdata-today.tar.gz ESdataBigger.tar.gz
else
if [ "$today" -gt 50000000 ];
   then
mv ESdata-today.tar.gz ESdata.tar.gz
fi
fi
 

The 50MB size would be the minimum expected for it, that if smaller chances are you've lost lots of data: adjust to your needs (over time).