Self-host Snipe-IT with Levelrail

IT asset management for tracking hardware, licenses, and accessories, and who currently has what.

  • Memory512 MiB
  • Archarm64
  • Services2

How to self-host Snipe-IT

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • mariadb:11
    • snipe/snipe-it:v7.1.16
  2. Create the app

    2 services start in a single Compose app, with 2 named volume mounts for your data, on port 80.

  3. Fill in the secrets

    3 secrets are generated and stored encrypted, 8 settings are preset, 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.

Snipe-IT requirements

Memory
About 512 MiB
Architectures
amd64 image published, arm64 image published
Ports
80
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
not yet recorded
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 80 on the host, so open them in the VPS firewall only if you want that.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Snipe-IT. 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 Snipe-IT docs page.

Deploy Snipe-IT your way

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

Deploy Snipe-IT from the CLI

levelrail-cli templates deploy snipe-it --name my-snipe-it

Deploy Snipe-IT 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/snipe-it/deploy

Snipe-IT configuration

Snipe-IT services

ServiceImagePortsVolumes
db mariadb:11 none snipeit_db_data -> /var/lib/mysql
snipeit snipe/snipe-it:v7.1.16 80 snipeit_data -> /var/lib/snipeit

Snipe-IT environment variables

VariableServiceValue
MYSQL_DATABASE db Preset by the template
MYSQL_PASSWORD db Generated at deploy
MYSQL_RANDOM_ROOT_PASSWORD db Preset by the template
MYSQL_USER db Preset by the template
APP_KEY snipeit Generated at deploy
APP_URL snipeit Preset by the template
MYSQL_DATABASE snipeit Preset by the template
MYSQL_PASSWORD snipeit Generated at deploy
Show all 11 variables
  • MYSQL_PORT_3306_TCP_ADDRsnipeitPreset by the template
  • MYSQL_PORT_3306_TCP_PORTsnipeitPreset by the template
  • MYSQL_USERsnipeitPreset by the template

Ports and volumes

Ports
80
Volumes
2 named mounts: snipeit_db_data -> /var/lib/mysql, snipeit_data -> /var/lib/snipeit

Snipe-IT FAQ

How much memory does Snipe-IT need?

The catalog lists about 512 MiB of memory for Snipe-IT across its 2 services.

Does Snipe-IT run on arm64?

For Snipe-IT, an arm64 image is published; amd64 is image published.

Does Snipe-IT need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which database does Snipe-IT bundle?

The template includes MySQL, running as its own service.

Which ports does Snipe-IT use?

Snipe-IT listens on port 80 inside the stack.

Where does Snipe-IT keep its data?

In named volumes: snipeit_db_data mounted at /var/lib/mysql and snipeit_data mounted at /var/lib/snipeit.

Can I deploy Snipe-IT on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id snipe-it for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image mariadb:11, snipe/snipe-it:v7.1.16 is what you deploy there.

levelrail-cli templates deploy snipe-it --name my-snipe-it