Docker Requirements and Limitations

Below are the requirements and limitations when running your own instance of Sublime in Docker

Requirements

MailboxesRAMCPUsStorage
108GB450GB
10016GB8100GB
60032GB16200GB
  • Supported architectures:
    • amd64 / x86_64
    • arm64 (including Apple Silicon -- M1/M2 Macs)
  • Supported operating systems:
    • Linux (Tested on Ubuntu 18-22.10, Amazon Linux 2, CentOS 7, and Fedora 34-37)
      • Recommended: Ubuntu 22.10
    • macOS
  • The following ports will need to be accessible when deployed remotely:
    • 3000: Used by the Sublime Dashboard
    • 8000: Used by the Sublime API
    • 443: If using SSL
    • 80: If using SSL
  • Docker version: 20.10.0 or greater
    Run docker version to see your Docker version
  • Git version: 2.7.0 or greater
    Run git version to see your Git version
  • docker compose version: 2.4.0 or greater
    Run docker compose version to see your Docker Compose version
    • Linux: comes installed with Docker engine but you can also do the standalone installation
    • macOS: comes installed with Docker Desktop

Docker deployment limitations

  • This Docker deployment is intended for small-medium size deployments or for testing purposes, and should not be used for more than 600 active mailboxes. If you'd like to activate more than 600 mailboxes, use the AWS Cloud-native deployment or Sublime Cloud, which can support any number of mailboxes.
  • The Docker deployment is "polling" based, opposed to callback/subscription based, so there’s naturally at least a 15 second delay between polling intervals when checking for new messages that have arrived. You may see a longer delay with more mailboxes. The cloud-native deployments are callback-based (i.e. push instead of pull), and real-time.
  • System updates bring the platform fully down, so mailboxes are not protected when standard updates are applied. Downtime for typical updates is usually short (less than a minute), but larger updates could take longer.
  • Downloading the raw EML for unflagged messages isn't currently supported due to raw message retention limitations.
  • Audit log export to S3 currently isn't supported.
  • Message analysis time is slower than cloud-native deployments, and there is no auto-scaling. Inference for some machine learning models are most performant on GPUs, which currently isn't supported via our Docker containers.
  • Enterprise monitoring is more limited for Docker based deployments.
  • No built-in backups or instrumentation for backups.
  • Child orgs are not supported

Usage data

Basic information like version, error logs, and high-level usage metrics are shared with the Sublime Team so we can troubleshoot issues, provide support, and make Sublime better for you and the community. You can change these settings in your Account page.