![]() ![]() This document will help you install the Portainer Server container on your Linux. Once you have 1 tool per container, you can start to compose and automate these pieces with a container orchestrator, eg Kubernetes, and building workflows to kick off tools based on outputs and results from previous tools, eg nmap container revealed ports 5432 or 3306 -> trigger sqlmap containers, or nmap container fingerprinted a domain as a wordpress site -> trigger wpscan container. Both elements run as lightweight Docker containers on a Docker engine. Not to mention, kali docker images can grow in size rather quickly (not uncommon to see 1 kali container eat up 4GB of storage disk), so this separation would make it easier to prune storage.īetter composability and automation. This will resume the container in whatever state you left it after running the initial docker run command or the last docker start and docker attach sequence. 1 tool per container not only allows the container to start up much faster, but gives you fine grain controls over each tool, eg metasploit container would only expose docker ports needed for metasploit. ![]() ![]() Why start out with an empty Kali Linux base image only to apt update, apt install, and configure a bunch of tools when I can have these tools ready to go in their respective containers, eg docker run -it wpscan. I also started using Kali in Docker 5 years ago or so, but I quickly moved on from that to 1 tool per container (alpine or debian) for a number of reasons:īetter user experience.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |