Self-host ActiveMQ Classic with Levelrail

A message broker with JMS, AMQP and MQTT support and a web console, with a data volume. The console login is admin with the password admin, so change it right after the first sign in.

  • Authorapache
  • LicenceApache-2.0
  • Memory512 MiB
  • Services1

How to self-host ActiveMQ Classic

  1. Pull the images

    One image is pulled on your server.

    Show images
    • apache/activemq-classic:6.1.4
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on ports 8161, 61616.

  3. Fill in the secrets

    You do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

After the first start

  • Sign in to the console as admin with the password admin and change it, because it is public knowledge. Connect clients at activemq:61616.

ActiveMQ Classic requirements

Memory
About 512 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
8161, 61616
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
Apache-2.0, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then ActiveMQ Classic. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the ActiveMQ Classic docs page.

Deploy ActiveMQ Classic your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy ActiveMQ Classic from the CLI

levelrail-cli templates deploy activemq --name my-activemq

Deploy ActiveMQ Classic with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/activemq/deploy

ActiveMQ Classic configuration

ActiveMQ Classic services

ServiceImagePortsVolumes
activemq apache/activemq-classic:6.1.4 8161, 61616 activemq_data -> /opt/apache-activemq/data

ActiveMQ Classic environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
8161, 61616
Volumes
1 named mount: activemq_data -> /opt/apache-activemq/data

ActiveMQ Classic FAQ

How much memory does ActiveMQ Classic need?

The catalog lists about 512 MiB of memory for ActiveMQ Classic.

Does ActiveMQ Classic run on arm64?

For ActiveMQ Classic, arm64 support is not confirmed; amd64 is unknown.

What licence is ActiveMQ Classic under?

ActiveMQ Classic is licensed under Apache-2.0, which is permissive, with few conditions on reuse.

Does ActiveMQ Classic need configuration before it starts?

No. The template fills in its own defaults.

Which ports does ActiveMQ Classic use?

ActiveMQ Classic listens on ports 8161 and 61616 inside the stack.

Where does ActiveMQ Classic keep its data?

In a named volume: activemq_data mounted at /opt/apache-activemq/data.

Can I deploy ActiveMQ Classic on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for ActiveMQ Classic, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image apache/activemq-classic:6.1.4 is what you deploy there.

levelrail-cli templates deploy activemq --name my-activemq