Portainer Templates logo

Portainer Templates

Snibox (container) Snibox (container)

OtherTools

Self-hosted snippet manager.

Image details

Pulls: 822k
Architecture: amd64
Image size: 346 MB
User: snowmean
Created: Oct 29, 2018
Updated: 5 years ago
Status: active

Configuration

Type
Container
Platform
linux
Image
snowmean/snibox-sqlite:latest
Ports
3010:3000/tcp
Volumes
/app/db/database : /portainer/Files/AppData/Config/Snibox
Restart
unless-stopped

Template by mikestraney

Notes

Label-oriented interface with search. Supports various programming languages, markdown, plain text.

Standalone Install

Select an install method, to see config/commands for deploying Snibox (container)

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Snibox (container), fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

More install options in our documentation.

snibox-sqlite

Snibox container working with SQLite3 database for personal use
To build this container use following command:
git clone https://gitlab.com/pivpav/snibox-sqlite.git
docker build -t snibox ./snibox-sqlite

Alternatively you can pull ready to use image from Docker Hub
docker pull snowmean/snibox-sqlite:latest

Container runs rake db:migrate on every start, in order to create database file if not exist, or update database scheme if required, so backups are highly recommended.
To run this container you might use following command:
docker run -d --name snibox \
              --volume /path/to/local/db:/app/db/database \
              --publish 80:3000 \
              --restart always \
              snowmean/snibox-sqlite

Environment variables

DATABASE - Defines sqlite3 database file location within container.
Default: /app/db/database/snibox.sqlite3
SECRET_KEY_BASE - Defines secret_key_base parameter for your Rails application. Default one is included into the image already, but general recommendation is to change it.
LOGLEVEL - Defines logging level for Rails application. Available options are: debug, info, warn, error and fatal
Default: debug

Dockerfile

For further questions please check Dockerfile on GitLab

Serve Snibox (container) on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying snibox-container.example.com to http://Snibox:3000

Add this to your Caddyfile

snibox-container.example.com {
	reverse_proxy http://Snibox:3000
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs Snibox
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:3010 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :3010
  • Stop the other service, or pick a different host port. In 3010:3000 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:3010. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, Snibox can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 3010

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/Snibox

Image won't pull

Test the pull directly on the host: docker pull snowmean/snibox-sqlite:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect Snibox --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A single container

Snibox (container) runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything Snibox (container) needs bundled into one download. This template pulls snowmean/snibox-sqlite:latest, which Docker fetches once (about 346 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Snibox (container)'s comes from Docker Hub, published by snowmean.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, so it runs on regular x86 PCs and servers, though not ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. A mapping like 3010:3000 means it's reachable on port 3010 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:3010 in a browser. It opens:

  • 3010:3000, likely the web interface

Volumes

A volume is where Snibox (container) keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /app/db/database from /portainer/Files/AppData/Config/Snibox on the host

Restart policy

The restart policy here is unless-stopped, so Docker restarts Snibox (container) after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Nothing custom is set, so Snibox (container) sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container Snibox. That's what you'll spot in the containers list and use in commands like docker logs Snibox.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Snibox (container) up. Add the template list to Portainer once, then deploying Snibox (container) is a click rather than a wall of config.