This project comprises a Docker image that runs a MikroTik's RouterOS virtual machine inside QEMU.

It's designed to simulate MikroTik's RouterOS environment, making it an excellent tool for development and testing purposes, especially for those working with the RouterOS API.

This Docker image is particularly useful for unit testing the routeros-api-php library, allowing developers to test applications in a controlled environment that closely mimics a real RouterOS setup.

For users seeking a fully operational RouterOS environment for production use within Docker, the VR Network Lab project is recommended as an alternative.

To use the image directly from Docker Hub, you can pull it and run a container as shown below. This will start a RouterOS instance with ports configured for SSH, API, API-SSL, and VNC access.

docker pull evilfreelancer/docker-routeros
docker run -d -p 2222:22 -p 8728:8728 -p 8729:8729 -p 5900:5900 -ti evilfreelancer/docker-routeros

For those preferring docker-compose, an example configuration is provided below. More examples is here.

version: "3.9"
services:
  routeros:
    image: evilfreelancer/docker-routeros:latest
    restart: unless-stopped
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun
      - /dev/kvm
    ports:
      - "2222:22"
      - "23:23"
      - "80:80"
      - "5900:5900"
      - "8728:8728"
      - "8729:8729"

You can easily create your own Dockerfile to include custom scripts or configurations. The Docker image supports various tags, which are listed here. By default, the latest tag is used if no tag is specified.

FROM evilfreelancer/docker-routeros
ADD ["your-scripts.sh", "/"]
RUN /your-scripts.sh

If you prefer to build the Docker image from source, the commands below will guide you through cloning the repository, building the image, and running a RouterOS container.

git clone https://github.com/EvilFreelancer/docker-routeros.git
cd docker-routeros
docker build . --tag ros
docker run -d -p 2222:22 -p 8728:8728 -p 8729:8729 -p 5900:5900 -ti ros

After launching the container, you can access your RouterOS instance via VNC (port 5900) and SSH (port 2222).

The table below summarizes the ports exposed by the Docker image, catering to various services and protocols used by RouterOS.

For more insights into Docker and virtualization technologies related to RouterOS and networking, explore the following resources:

• Mikrotik RouterOS in Docker using Qemu - An article on Habr that provides a guide on setting up Mikrotik RouterOS in Docker using Qemu, ideal for developers and network engineers interested in RouterOS virtualization.
• RouterOS API Client - GitHub repository for the RouterOS API PHP library, useful for interfacing with MikroTik devices.
• VR Network Lab - A project for running network equipment in Docker containers, recommended for production-level RouterOS simulations.
• qemu-docker - A resource for integrating QEMU with Docker, enabling virtual machine emulation within containers.
• QEMU/KVM on Docker - Demonstrates using QEMU/KVM virtualization within Docker containers for improved performance.