DockerTrap is Docker based honeypot that creates new, isolated, firewalled containers for each IP address that tries to connect to the host. Any Docker image can now be used as a honeypot! No restrictions!

sudo apt -y install apt-transport-https ca-certificates curl software-properties-common
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu bionic stable"
sudo apt update
apt-cache policy docker-ce
sudo apt -y install docker-ce

sudo apt-get update
sudo apt-get install socat xinetd auditd netcat-openbsd

Copy honeypot to /usr/bin/honeypot and honeypot.clean to /usr/bin/honeypot.clean and make them executable. You may have to customize the ports in the iptables rules, the memory limit of the container and the network quota if you want to run anything other than an SSH honeypot on port 22.

Add the following line to /etc/crontab. This runs the cleanup script to check for old containers every 5 minutes.

*/5 * * * * /usr/bin/honeypot.clean

Create the following service file in /etc/xinetd.d/honeypot and add the line honeypot 22/tcp to /etc/services to keep xinetd happy.

# Container launcher for an SSH honeypot
service honeypot
{
        disable         = no
        instances       = UNLIMITED
        server          = /usr/bin/honeypot
        socket_type     = stream
        protocol        = tcp
        port            = 22
        user            = root
        wait            = no
        log_type        = SYSLOG authpriv info
        log_on_success  = HOST PID
        log_on_failure  = HOST
}

Enable logging the execve systemcall in auditd by adding the following audit rules:

auditctl -a exit,always -F arch=b64 -S execve
auditctl -a exit,always -F arch=b32 -S execve

A Dockerfile for a base image is included in the alpinetrap directory and sets to root password to root by default. You can create and configure your own base image without restriction. The container will spin up and be managed by xinitd normally. Any initialization is up to you.

Make sure to commit the image as "honeypot:latest". You may also wish to create additional accounts named user, guest, admin, temp, etc., and give them weak passwords like 1234, or password to let brute-force attackers crack your host easily. The IP address of the attacker's host is passed to the container in the environment variable REMOTE_HOST. For logging, you may want to configure an rsyslog instance to forward logs to the host machine.

1. Firewall rules are bugged and more restrictive than intended
2. Logging with auditd is still bugged and not working as intended
3. Docker API honeypot apitrap.sh will be replaced by something like Whaler (redirected from a secured host, possibily on a per-instanced basis like DockerTrap), but should appear as an unsecured host to each honeypot
4. Auto-installer

Thanks goes to Peter Kasza for the origional Dockerpot; brilliant work!