![OmniTools]()
OmniTools
Container
Toolbox of over a hundred small utilities for images, PDFs, video, audio, text, JSON, CSV and lists, like resizing, compressing, merging, trimming and converting, all run in your browser so files never reach the server. Source: https://github.com/iib0011/omni-tools
Image details
Source details
Configuration
TypeContainerlinuxiib0011/omni-tools:latest8920:80/tcpunless-stoppedTemplate by NotAFlightRisk
Report issueNotes
http://<your-host>:8920. There's no login and nothing to back up, since every tool works on your files inside the browser. Over plain http from another machine, the video, audio and GIF tools fail and the copy buttons do nothing, because the browser only allows what they need on HTTPS or localhost. Everything else, PDFs and images included, works fine, and Download still saves results. Put it behind an HTTPS reverse proxy and they all work. Those video and audio tools fetch ffmpeg from unpkg.com, PDF compression fetches Ghostscript from a CDN, and icons load from api.iconify.design. Docs: github.com/iib0011/omni-toolsStandalone Install
Select an install method, to see config/commands for deploying OmniTools
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select OmniTools, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
More install options in our documentation, or see iib0011/omni-tools for app-specific guidance.
OmniTools
Useful online tools for everyone. Have a look !.docker run -d -p 8080:80 --name omni-tools -it iib0011/omni-toolsCredits
Coded with ❤️ by Ibrahima G. Coulibaly.License
This project is under the MIT license.Serve OmniTools 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 omnitools.example.com to http://omnitools:80
Add this to your Caddyfile
omnitools.example.com {
reverse_proxy http://omnitools:80
}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 omnitools - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Port already in use
If deployment fails with "Bind for 0.0.0.0:8920 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :8920 - Stop the other service, or pick a different host port. In
8920:80only 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:8920. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, omnitools can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 8920
Image won't pull
Test the pull directly on the host: docker pull iib0011/omni-tools: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 loginto 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, arm64 - 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 omnitools --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Data disappears when the container is recreated
This template doesn't define any volumes, so everything omnitools saves lives inside the container and is lost on update or recreate.
- Add a volume mapping for omnitools's data folder before storing anything you care about.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue on iib0011/omni-tools
- Template not working: Open an issue on NotAFlightRisk/portainer-templates-extras
- This website not working: Open an issue on lissy93/portainer-templates
A single container
OmniTools 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 OmniTools needs bundled into one download. This template pulls iib0011/omni-tools:latest, which Docker fetches once (about 37 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. OmniTools's comes from Docker Hub, published by iib0011.
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. Newest right now is 0.7. 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, arm64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.
Ports
A port is the door the app answers on. A mapping like 8920:80 means it's reachable on port 8920 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:8920 in a browser. It opens:
8920:80, likely the web interface
No stored data
This template doesn't mount any storage, so whatever OmniTools writes stays inside the container and is wiped if it's recreated or updated. That's fine for something stateless, but add a volume before trusting it with anything you want to keep.
Restart policy
The restart policy here is unless-stopped, so Docker restarts OmniTools 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 OmniTools 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 omnitools. That's what you'll spot in the containers list and use in commands like docker logs omnitools.
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.
Open source license
OmniTools is open source, released under the MIT license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set OmniTools up. Add the template list to Portainer once, then deploying OmniTools is a click rather than a wall of config.