linuxserver/snipe-it ¶

Snipe-it makes asset management easy. It was built by people solving real-world IT and asset management problems, and a solid UX has always been a top priority. Straightforward design and bulk actions mean getting things done faster.

Supported Architectures¶

We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling lscr.io/linuxserver/snipe-it:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

Architecture	Available	Tag
x86-64	✅	amd64-<version tag>
arm64	✅	arm64v8-<version tag>
armhf	❌

Application Setup¶

Access the webui at <your-ip>:8080, for more information check out Snipe-it.

This container requires a MySQL or MariaDB server to connect to, we recommend ours

Usage¶

To help you get started creating a container from this image you can either use docker-compose or the docker cli.

Info

Unless a parameter is flaged as 'optional', it is mandatory and a value must be provided.

docker-compose (recommended, click here for more info)¶

---
services:
  snipe-it:
    image: lscr.io/linuxserver/snipe-it:latest
    container_name: snipe-it
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - APP_KEY=
      - APP_URL=http://localhost:8080
      - MYSQL_PORT_3306_TCP_ADDR=
      - MYSQL_PORT_3306_TCP_PORT=
      - MYSQL_DATABASE=
      - MYSQL_USER=
      - MYSQL_PASSWORD=
      - APP_DEBUG=false #optional
      - APP_ENV=production #optional
      - APP_FORCE_TLS=false #optional
      - APP_LOCALE= #optional
      - MAIL_PORT_587_TCP_ADDR= #optional
      - MAIL_PORT_587_TCP_PORT= #optional
      - MAIL_ENV_FROM_ADDR= #optional
      - MAIL_ENV_FROM_NAME= #optional
      - MAIL_ENV_ENCRYPTION= #optional
      - MAIL_ENV_USERNAME= #optional
      - MAIL_ENV_PASSWORD= #optional
    volumes:
      - /path/to/snipe-it/data:/config
    ports:
      - 8080:80
    restart: unless-stopped

docker cli (click here for more info)¶

docker run -d \
  --name=snipe-it \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -e APP_KEY= \
  -e APP_URL=http://localhost:8080 \
  -e MYSQL_PORT_3306_TCP_ADDR= \
  -e MYSQL_PORT_3306_TCP_PORT= \
  -e MYSQL_DATABASE= \
  -e MYSQL_USER= \
  -e MYSQL_PASSWORD= \
  -e APP_DEBUG=false `#optional` \
  -e APP_ENV=production `#optional` \
  -e APP_FORCE_TLS=false `#optional` \
  -e APP_LOCALE= `#optional` \
  -e MAIL_PORT_587_TCP_ADDR= `#optional` \
  -e MAIL_PORT_587_TCP_PORT= `#optional` \
  -e MAIL_ENV_FROM_ADDR= `#optional` \
  -e MAIL_ENV_FROM_NAME= `#optional` \
  -e MAIL_ENV_ENCRYPTION= `#optional` \
  -e MAIL_ENV_USERNAME= `#optional` \
  -e MAIL_ENV_PASSWORD= `#optional` \
  -p 8080:80 \
  -v /path/to/snipe-it/data:/config \
  --restart unless-stopped \
  lscr.io/linuxserver/snipe-it:latest

Parameters¶

Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.

Ports (`-p`)¶

Parameter	Function
`8080:80`	Snipe-IT Web UI

Environment Variables (`-e`)¶

Env	Function
`PUID=1000`	for UserID - see below for explanation
`PGID=1000`	for GroupID - see below for explanation
`TZ=Etc/UTC`	specify a timezone to use, see this list.
`APP_KEY=`	App key used for encrypting stored data. Generate with `docker exec snipe-it php /app/www/artisan key:generate --show`.
`APP_URL=http://localhost:8080`	Hostname or IP and port if applicable, be sure to define https/http
`MYSQL_PORT_3306_TCP_ADDR=`	Mysql hostname or IP to use
`MYSQL_PORT_3306_TCP_PORT=`	Mysql port to use
`MYSQL_DATABASE=`	Mysql database to use
`MYSQL_USER=`	Mysql user to use
`MYSQL_PASSWORD=`	Mysql password to use
`APP_DEBUG=false`	Set to `true` to see debugging output in the web UI.
`APP_ENV=production`	Default is `production` but can use `testing` or `develop`.
`APP_FORCE_TLS=false`	Set to `true` if running behind a reverse proxy
`APP_LOCALE=`	Default is `en-US`. Set to a language from this list.
`MAIL_PORT_587_TCP_ADDR=`	SMTP mail server ip or hostname.
`MAIL_PORT_587_TCP_PORT=`	SMTP mail server port.
`MAIL_ENV_FROM_ADDR=`	The email address mail should be replied to and listed when sent.
`MAIL_ENV_FROM_NAME=`	The name listed on email sent from the default account on the system.
`MAIL_ENV_ENCRYPTION=`	Mail encryption to use e.g. `tls`.
`MAIL_ENV_USERNAME=`	SMTP server login username.
`MAIL_ENV_PASSWORD=`	SMTP server login password.

Volume Mappings (`-v`)¶

Volume	Function
`/config`	Contains your config files and data storage for Snipe-IT

Miscellaneous Options¶

Parameter	Function

Environment variables from files (Docker secrets)¶

You can set any environment variable from a file by using a special prepend FILE__.

As an example:

-e FILE__MYVAR=/run/secrets/mysecretvariable

Will set the environment variable MYVAR based on the contents of the /run/secrets/mysecretvariable file.

Umask for running applications¶

For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.

User / Group Identifiers¶

When using volumes (-v flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=1000 and PGID=1000, to find yours use id your_user as below:

id your_user

Example output:

uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)

Docker Mods¶

We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.

Support Info¶

Shell access whilst the container is running:
```
docker exec -it snipe-it /bin/bash
```
To monitor the logs of the container in realtime:
```
docker logs -f snipe-it
```

Container version number:

docker inspect -f '{{ index .Config.Labels "build_version" }}' snipe-it

Image version number:

docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/snipe-it:latest

Updating Info¶

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.

Below are the instructions for updating containers:

Via Docker Compose¶

Update images:

All images:
```
docker-compose pull
```
Single image:
```
docker-compose pull snipe-it
```

Update containers:

All containers:
```
docker-compose up -d
```
Single container:
```
docker-compose up -d snipe-it
```

You can also remove the old dangling images:
```
docker image prune
```

Via Docker Run¶

Update the image:

docker pull lscr.io/linuxserver/snipe-it:latest

Stop the running container:
```
docker stop snipe-it
```
Delete the container:
```
docker rm snipe-it
```
Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
You can also remove the old dangling images:
```
docker image prune
```

Image Update Notifications - Diun (Docker Image Update Notifier)¶

Tip

We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.

Building locally¶

If you want to make local modifications to these images for development purposes or just to customize the logic:

git clone https://github.com/linuxserver/docker-snipe-it.git
cd docker-snipe-it
docker build \
  --no-cache \
  --pull \
  -t lscr.io/linuxserver/snipe-it:latest .

The ARM variants can be built on x86_64 hardware and vice versa using lscr.io/linuxserver/qemu-static

docker run --rm --privileged lscr.io/linuxserver/qemu-static --reset

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

To help with development, we generate this dependency graph.

Init dependency graph

Versions¶

17.06.24: - Rebase to Alpine 3.20. Existing users should update their nginx confs to avoid http2 deprecation warnings.
06.03.24: - Existing users should update: site-confs/default.conf - Cleanup default site conf.
17.02.24: - Add php81-exif.
03.07.23: - Deprecate armhf. As announced here
13.04.23: - Move ssl.conf include to default.conf.
13.04.23: - Add php81-pecl-redis for redis support.
28.12.22: - Rebase to Alpine 3.17, migrate to s6v3.
20.08.22: - Rebasing to alpine 3.15 with php8. Restructure nginx configs (see changes announcement).
14.05.22: - Add php7-sodium for v6.
12.04.22: - Don't build development elements.
02.03.22: - Rework init logic, do not show default compose.
29.06.21: - Rebasing to alpine 3.14.
30.04.21: - Rebasing to alpine 3.13, add artisan migrate on spinup.
01.06.20: - Rebasing to alpine 3.12.
19.12.19: - Rebasing to alpine 3.11.
28.06.19: - Rebasing to alpine 3.10.
10.04.19: - Add php deps for V4.7.0, ensure framework directories are available at build time.
10.04.19: - Fix permissions for new bootstrap cache directory.
23.03.19: - Switching to new Base images, shift to arm32v7 tag.
22.02.19: - Rebasing to alpine 3.9.
31.10.18: - Rebasing to alpine 3.8
05.08.18: - Migration to live build server.
13.06.18: - Initial Release.

linuxserver/snipe-it¶