Public | Automated Build

Last pushed: 16 hours ago
Short Description
An image of the famous Metasploit-Framework tool for pentesting.
Full Description

Metasploit Framework dockerfile


This Dockerfile builds a Debian-based Docker container with Metasploit-Framework installed.

A quick and easy way to deploy Metasploit on any box, including Linux, MacOS or Windows!

MSF is started automatically with:

  • all dependencies installed,
  • automatic updates at startup,
  • a connection with the local Postgres database,
  • volumes, to share data and get access to your custom Metasploit scripts.

It also includes:

  • tmux, to use multiple windows (msfconsole, shell, etc.) inside the container;
  • nmap, the famous network scanner (along with ncat);
  • nasm, to support custom encoders;
  • a configuration file to get an improved prompt in Metasploit, with timestamping and sessions/jobs status.


To build the container, just use this command:

docker build -t phocean/msf .

Docker will download the Debian image and then execute the installation steps.

Be patient, the process can be quite long the first time.

Note that you may want to:

  • copy the contrib/config file to the ~/.msf4 folder to get a nice prompt.
  • customize the conf/tmux file, if you plan to use this tool.

The configuration of Tmux maps the keyboard as in Screen (CTRL-A). It also makes a few cosmetic changes to the status bar.

Note that you could adjust the init script to automatically launch Tmux with a msf window and a bash one, for instance. I don't make it the default, because I don't want to bother people who don't need/want Tmux.*


Once the build process is over, get and enjoy a neat msf prompt with this command:

docker run --rm -i -t -p 9990-9999:9990-9999 -v /home/<USER>/.msf4:/root/.msf4 -v /tmp/msf:/tmp/data --name msf phocean/msf


  • We map the port range from 9990 to 9999 to our host, to catch reverse shells back.
  • We mount the local .msf4 folder, where you can set your prompt and put custom scripts and modules, to /root/.msf4 inside the container (if you want to make some changes at runtime, beware to do it from your host, not from within the container).
  • Similarly, we mount a /tmp/data folder to exchange data (a dump from a successful exploit, for instance).

Of course, it is up to you to adjust it to your taste or need.

You can also give it full access to the host network:

Note that this can be risky as all services on your host, including those that listen on localhost, would be reachable from within the container, in case it is compromise.

docker run --rm -it --net=host -v /home/<USER>/.msf4:/root/.msf4 -v /tmp/msf:/tmp/data --name msf phocean/msf

At any time, you can exit, which only stops (suspend) the container.

Because of the --rm, the container itself is not persistent.

Persistency is however partially made throught the mounting of your local folders (history, scripts).
So if you want to restart a session, just re-run the docker.

I find it more convenient, but if, for some reason, you prefer to keep the container, just remove the --rm and then you can restart the stopped container anytime:

docker restart msf
docker attach msf
# Later:
docker rm msf


After launching the docker container, you will get a bash prompt.

From there, you can start msfconsole, tmux or any other Metasploit tool (msfvenom, pattern_offset.rb, etc.).

Docker Pull Command

Comments (0)