Monarch C2
  • Introduction to Monarch
  • Installation
    • Resources
    • Uninstall Monarch
  • Interface
  • Features
    • External integration
    • Multiplayer
    • Management (server)
    • HTTP customization
  • Architecture
  • Usage
    • Builders
    • Agents
    • Listeners
    • Stage
    • Sessions
    • Players (server)
    • Chat
  • Integration
    • Project configuration
    • Builder
      • Architecture
      • API
      • Build routine
      • Build service
    • C2 server
      • Registering implants
      • Talking to implants
    • Implant development
      • Registration
      • Tasks
      • The TCP handler
Powered by GitBook
On this page
  • Docker
  • Monarch-as-a-Container
  1. Installation

Resources

Resources created by Monarch on installation

Docker

On native installation of Monarch, a single MySQL container named monarch-sql is created, which is the primary database for all Monarch data. It is a persistent container, meaning that it will start itself after a restart unless it was manually stopped by anyone.

Additionally, a monarch-net network is created for all container instances to use. Grouping them with a network ID is useful if say, for example, you wanted to delete all Monarch-owned resources conveniently.

Monarch-as-a-Container

When Monarch is installed on a container, this container, monarch-ctr, is added to monarch-net in addition to the SQL database.

Last updated 1 year ago