garo/suicide repository overview

⁠Suicide Docker

This image is not meant to help you. It's purpose is to be dangerous and break your system.

⁠Important warning:

Only use this if you are absolutely sure what you are doing !
If you do decice to use this, remember that things will break and that YOU are the only one responsible for this.
I will NOT take any responsiblity at all !

This repository uses the GPLv3 license which clearly mentions:
"This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
See the file LICENSE for details.

⁠What this is:

Most programs I added in this image are meant to break:

• The container itself
• Other running containers
• The hostsystem
• The networkconnection
• Everything connected to the hostsystem

The idea behind this is is to test your skills in managing containers in a safe way.
You can use these programs to do so damage and try to find mothods to work around the resulting problems.
If you manage this then you should be able to find a way around similar programs in your real containers.

Another use might be to use this as base image to create a image with some software of which you want to test the resilience.

⁠Building the image

This image is also available as garo/suicide on Dockerhub with different tags for different base images (from different distributions)

• If you have Perl and the modules Getopt::Long and File::Temp: Use ./buildimage.pl ( See ./buildimage.pl --help if you want to tweak the buildprocedure )
• Otherwise, tune Dockerfile manually and run docker build with your favorite options

⁠Included software

• dd → break your (virtual) disk/memory/filesystem in all possible ways
• rm and mv → (re)move all your files
• cp and touch → create an overload of files
• cat → overwrite your files and/or enlarge them
• mkfs, mktemp → combine it with previous tools to cause similar damage in RAM
• nping → break your network
• thc-ipv6 → break your IPv6 network
• stress-ng → break everything
• buildtools (gcc, perl, libraries, ...) → write your own tools (please send PR's if you do)
• vim → edit your code
• forkbomb → break your pidlist (improve it and send PR's)